Grant terraform-infra kv metadata read #113
Reference in New Issue
Block a user
Delete Branch "benvin/infra-kv-metadata"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Follow-up to the merged #111 (which shipped
kv/data/service/terraform/infraread only).terraform-infra's providers.tf uses avault_kv_secret_v2data source, which reads the kv-v2 metadata path on every plan/apply (same behaviour that 403'd a prior terraform-git apply — seepolicies/kv/service/vault/.../gitea/config_write.yaml). Addkv/metadata/service/terraform/infraread so the plan doesn't 403 once the secret is seeded.Verified against terraform-infra PR #5:
skip_child_tokencleared the child-token 403 and the data-read policy works (plan now reaches "no secret found"); metadata read is the remaining policy gap before a seeded plan can pass.https://claude.ai/code/session_01JUoARVdmhxKQHyyyp1pxeT