net-kingdom/sso-mfa/k8s/keycape/secrets-engine-openbao-client.proposed.patch.yaml
tegwick a1e7302930
All checks were successful
CI Smoke / host-smoke (push) Successful in 1s
CI Smoke / container-smoke (push) Successful in 2s
Prepare the secrets-engine-openbao KeyCape client registration as source only
Owner-specific exact-match merge and rollback for sso/keycape-config, the one
proposed env secretKeyRef, synthetic tests and NK-WP-0046 for KEY-WP-0037-T03.
Nothing is applied; the live rollout waits on decision caafe4be.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 132360@bnt-lap001
Assistant-Session: 769b1afd-4330-4c86-96b2-e510e26db42b
2026-10-06 13:35:12 +02:00

17 lines
762 B
YAML

# PROPOSED, NOT APPLIED. KEY-WP-0037-T03 / NK-WP-0046.
# Adds exactly one env binding to sso/keycape; values never appear here.
# Prerequisites: platform has materialised Secret keycape-secrets-engine-openbao-client
# (key client-secret) and the founder's live go (decision caafe4be) is resolved.
# Apply as a strategic-merge patch (env merges by name), server dry-run and diff
# first; then fold into deployment.yaml in the same change that records the go.
spec:
template:
spec:
containers:
- name: keycape
env:
- name: KEYCAPE_SECRETS_ENGINE_OPENBAO_CLIENT_SECRET
valueFrom:
secretKeyRef:
name: keycape-secrets-engine-openbao-client
key: client-secret