-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OCI registry-backed blueprints #147
Comments
There's no direct way to specify a list of OCI uris to use as blueprint instances, but as you can manage any model via blueprint instance, you can use a blueprint that creates more blueprints: version: 1
metadata:
name: OCI blueprints
entries:
- model: authentik_blueprints.blueprintinstance
identifiers:
name: my-blueprint-name
attrs:
context:
foo: bar
path: oci:https://ghcr.io/<username>/<package-name>:<ref>
- model: authentik_blueprints.blueprintinstance
identifiers:
name: my-other-blueprint-name
attrs:
context:
foo: bar
path: oci:https://ghcr.io/<username>/<package-name>:<ref> (the |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It appears that the helm chart has support for defining blueprints via a configmap. Is there a way to configure authentik to apply OCI registry-backed blueprints via the chart?
The text was updated successfully, but these errors were encountered: