unkinben
743ad5ac33
A live re-test showed the plugin's own NetBox calls (username resolution, cred minting) still 403 after the KV admin_token was re-seeded bare, because the mount uses ignore_changes=[token] and kept the old scheme-prefixed value. The plugin builds its admin Authorization header from the token value's nbt_ prefix, not from token_version, so a stale "Bearer nbt_..." value double-mangles into a malformed header. - Extend the netbox_secret_backend postcondition to also assert token_version matches the admin token kind (nbt_ v2 <-> token_version 2; bare v1 <-> 1), so a version/token mismatch fails at plan time with a clear message. - Document that token_version does not affect the admin header (only minted token version), and give the exact command to push a corrected token into a running mount (vault write netbox/config token=<BARE>), warning against -replace which would drop the mount's roles.
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