website/docs: explain guarantees around blueprint ordering (#10595)

* Load blueprints in deterministic order.

* Update docs.

* Remove doc update

Signed-off-by: Mike Fotinakis <mike@fotinakis.com>

* Update documentation only.

---------

Signed-off-by: Mike Fotinakis <mike@fotinakis.com>
This commit is contained in:
Mike Fotinakis
2024-07-30 07:24:58 -04:00
committed by GitHub
parent 0faaedba9e
commit 105ab0d2ff
2 changed files with 8 additions and 0 deletions

View File

@ -36,6 +36,12 @@ To disable existing blueprints, an empty file can be mounted over the existing b
File-based blueprints are automatically removed once they become unavailable, however none of the objects created by those blueprints afre affected by this.
:::info
Please note that, by default, blueprint discovery and evaluation is not guaranteed to follow any specific order.
If you have dependencies between blueprints, you should use [meta models](/developer-docs/blueprints/v1/meta#authentik_blueprintsmetaapplyblueprint) to make sure that objects are created in the correct order.
:::
## Storage - OCI
Blueprints can also be stored in remote [OCI](https://opencontainers.org/) compliant registries. This includes GitHub Container Registry, Docker hub and many other registries.