unkinben
724fcf2a76
Why: applying the forthcoming gitea_secret_backend + role config from terraform-vault requires the deployment identity (tf_vault approle / woodpecker_terraform_vault k8s role) to write the engine's config and roles. Without it, the engine apply 403s. This mirrors policies/rancher/admin.yaml. Change: - Add policies/gitea/admin.yaml granting create/read/update/delete on gitea/config, create/update on gitea/config/rotate-root, and full manage on gitea/roles/*; excludes gitea/creds/* (minting is for consumers). - Catalog registration is already covered by the shared wildcard grant in policies/sys/plugins/catalog/admin.yaml and mounting uses existing sys/mounts/* access, so no new catalog/mount grant is added (matches rancher). 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