Why: terraform-git now provisions the gitea-vault-admin site-admin bot and
writes its generated password to kv/service/vault/au/syd1/secret_backend/gitea/config
so the gitea secrets engine can consume it at creation time. The
woodpecker_terraform_git / terraform_git identity has no write access to that
KV path, so its apply would 403 without this grant. The deployer that reads the
seed already has read via policies/kv/service/vault/secret_backends_read.yaml.
Change:
- Add policies/kv/service/vault/au/syd1/secret_backend/gitea/config_write.yaml
granting create/read/update on the gitea config KV path to the terraform_git
approle and woodpecker_terraform_git k8s role.
Claude-Session: https://claude.ai/code/session_015ur3i7D2azsMAWTSVABApv
unkinben
9c35b41ab1