unkinben
9c35b41ab1
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
terraform-vault
A repository to manage the configuration of Vault secret engines, authentication modes and policies.
Usage
- Initialize Terraform
Once you have your backend block configured, you need to initialize your Terraform working directory to configure the backend:
terraform init
This command initializes the backend and checks the connection to Consul. If everything is set up correctly, Terraform will start using Consul as its backend for storing the state.
- Common terraform init Errors
If you encounter errors while running terraform init, check the following:
Consul server is reachable: Make sure that the address is correct and that you can connect to the Consul server.
Consul token (if using ACLs): Verify that the token has the correct permissions to write to the specified path in the Consul KV store.
- Example Consul KV Structure
In Consul, the state file will be stored in the KV store under the specified path:
terraform/state
You can check the Consul KV store by accessing the Consul UI or using the consul kv command to see the stored Terraform state:
consul kv get terraform/state