Derive custody at platform/workloads/keycape/{client_id} (secret_ref is no
longer case-settable), reuse the workload-kv-read-keycape-* policy family with
templated bodies, add the external-secrets-keycape-{client_id} ESO role, name
the catalog entry {consuming_service}-keycape-client and collapse the duplicate
KV-path rollback. Schema and validator require a body on policy/role items.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 330051@bnt-lap001
Assistant-Session: b98d4912-95a3-4619-b7fb-57aa1db7407b
|
||
|---|---|---|
| .. | ||
| custody-record | ||
| emission-cadence-profile | ||
| iam-profile-conformance | ||
| playbook-capability-contract | ||
| posture-feedback | ||
| security-bootstrap-console | ||
| security-case-types | ||
| security-scenario-composer | ||
| tenancy-posture | ||
| sync-user-engine-delivery-secret.sh | ||