From 1f060bd9b0bc318d5db6b21174ec6a4236ce5f9a Mon Sep 17 00:00:00 2001 From: Ben Vincent Date: Mon, 27 Jul 2026 23:26:18 +1000 Subject: [PATCH] policies: allow terraform-git to delete the gitea config seed for taint recovery Claude-Session: https://claude.ai/code/session_015ur3i7D2azsMAWTSVABApv --- .../vault/au/syd1/secret_backend/gitea/config_write.yaml | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/policies/kv/service/vault/au/syd1/secret_backend/gitea/config_write.yaml b/policies/kv/service/vault/au/syd1/secret_backend/gitea/config_write.yaml index d325a0b..973e4d6 100644 --- a/policies/kv/service/vault/au/syd1/secret_backend/gitea/config_write.yaml +++ b/policies/kv/service/vault/au/syd1/secret_backend/gitea/config_write.yaml @@ -7,16 +7,22 @@ # write side for terraform-git's own identity. --- rules: + # delete is required for taint recovery and destroy (the resource got tainted + # by pipeline 107's failed post-create read and replace = delete+create). + # The seed's write-once semantics are enforced by lifecycle ignore_changes in + # terraform-git, not by withholding delete here. - path: "kv/data/service/vault/au/syd1/secret_backend/gitea/config" capabilities: - create - read - update + - delete # vault_kv_secret_v2 also reads the kv-v2 metadata path on every plan/apply # (403 here broke the terraform-git main apply, pipeline 107). - path: "kv/metadata/service/vault/au/syd1/secret_backend/gitea/config" capabilities: - read + - delete auth: approle: