Fix KV path comment in jellyfin-ldap provider configuration.
ci/woodpecker/pr/pre-commit Pipeline was successful
ci/woodpecker/pr/plan Pipeline was successful

Reference the actual Vault KV seed path for outpost token instead of deferring to PR body.
This commit is contained in:
2026-08-26 22:23:32 +10:00
parent 3396b399ce
commit 9760c2eb3f
+1 -1
View File
@@ -17,7 +17,7 @@
# authentik_application (slug jellyfin-ldap) and authentik_outpost # authentik_application (slug jellyfin-ldap) and authentik_outpost
# (name jellyfin-ldap-outpost, type ldap). The outpost's API token is generated # (name jellyfin-ldap-outpost, type ldap). The outpost's API token is generated
# by Authentik AFTER apply and must be seeded into KV for the k8s outpost # by Authentik AFTER apply and must be seeded into KV for the k8s outpost
# Deployment to consume (see PR body for the exact path). # Deployment to consume: kv/kubernetes/namespace/authentik/default/outpost-token (key: token).
name: Jellyfin LDAP name: Jellyfin LDAP
bind_flow: default-authentication-flow bind_flow: default-authentication-flow
unbind_flow: default-invalidation-flow unbind_flow: default-invalidation-flow