unkinben
b11a55edd9
Why: - The netbox secrets engine mount + roles land in a follow-up PR; its manage policy must exist first so the deployer can create the config and roles the moment the engine PR applies (policy-first split). How: - Add policies/netbox/admin.yaml granting the deployer netbox/config, netbox/config/rotate and netbox/roles/* (excludes netbox/creds/*), bound to the tf_vault AppRole and woodpecker_terraform_vault k8s role, mirroring the gpg/gitea admin policies.
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