unkin-agent
bb4db3e069
The master apply aborts reading the unseeded ghp config KV (kv/data/service/vault/au/syd1/secret_backend/ghp/config), blocking all changes including the arrstack plugin registration (#125). The ghp backend and role are not-yet-created (0 to destroy), so removing them is non-destructive and lets the apply proceed. The ghp plugin registration and ghp policies are retained. This is part 1 of remove -> grant write policy -> seed KV -> re-add; it will be reverted once the ghp config is seeded. - Remove module.ghp_secret_backend and module.ghp_secret_backend_role instantiations (and the role's depends_on) from modules/vault_cluster/main.tf. - Remove the ghp_secret_backend and ghp_secret_backend_role variables from modules/vault_cluster/variables.tf. - Remove the ghp_secret_backend and ghp_secret_backend_role parsing blocks from config/config.hcl. - Remove the ghp_secret_backend and ghp_secret_backend_role inputs from environments/au/syd1/terragrunt.hcl. - Delete config/ghp_secret_backend/ghp.yaml and config/ghp_secret_backend_role/ghp/agent.yaml.
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