unkinben
a8027c0794
Why: - The role file named its NetBox user in a netbox_username field that repeated the filename stem, and the value (svc-terraform-infra) drifted from the role name, so the engine role and the user it mints tokens for could disagree. How: - Derive netbox_username from the filename in config.hcl, alongside the role name, so the role name and NetBox username are the same value by construction. - Drop the netbox_username field from the role yaml so nothing in the file repeats what the filename already encodes.
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