-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Closed
Labels
Description
Describe the bug
When loading blueprints from an OCI registry I always get the error Blueprint file does not exist
To Reproduce
Steps to reproduce the behavior:
- Create a Blueprint
- Upload the Blueprint with oras
./oras push larsl.dev:5050/larsl-net/authentik-config/blueprints/larsl-stages-base:latest larsl-stages-base.yaml:application/vnd.goauthentik.blueprint.v1+yaml - Try loading the Blueprint with authentik
oci://larsl.dev:5050/larsl-net/authentik-config/blueprints/larsl-stages-base:latest
oci://ghcr.io/larsl-net/blueprint/larsl-stages-base:latest
Expected behavior
The Blueprint loading over OCI works.
Version and Deployment (please complete the following information):
- authentik version: 2023.5.2
- Deployment: docker-compose
Reactions are currently unavailable
