unkinben
bd1bcc2db9
Why: - The netbox secrets engine can only mint tokens for NetBox users that already exist, so today those service users must be hand-created before a role works. Consul already solves the equivalent problem declaratively, and NetBox should be managed the same way so Ben seeds only the engine admin token. How: - Add a netbox_user_management module mirroring consul_acl_management: it reads each backend's seeded admin token from KV, configures one e-breuninger/netbox provider per backend, and creates netbox_user + netbox_permission resources from a config-driven map (random unknown passwords, since these users authenticate only via Vault-minted tokens). - Drive it from config/netbox_user/<username>.yaml, scanned in config.hcl and wired through terragrunt inputs and the vault_cluster module, reusing the sanitized backend-alias pattern the Consul providers use. - Define the terraform-infra user 1:1 with the engine role, granting write on the IPAM/DCIM objects terraform-infra manages (prefixes, ip-addresses, ip-ranges, devices, interfaces, mac addresses, and the supporting role/tag/type objects). - Flip the terraform-infra role's netbox_username from svc-terraform-infra to terraform-infra so the engine role and NetBox username match exactly.
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