unkinben
702dc6c62f
Why: - The NetBox service identity was split across two files (config/netbox_user and config/netbox_secret_backend_role) that repeated the username three times: the filename, a netbox_username field, and the permission name. - Creating the engine role and creating its NetBox user are one act, so one file should describe the whole identity. How: - Make config/netbox_secret_backend_role/netbox/<name>.yaml the single source per identity: filename = engine role name = NetBox username, body = write access, TTLs, and an inline permissions block. - Derive netbox_username from the filename in config.hcl (keep netbox_user_id as an optional override), and drop the netbox_username field from the role yaml. - Iterate that same role map in the netbox_user_management module, keyed by config path, to synthesize the NetBox user and object permissions; default a single permission's name to the role name so nothing repeats the filename. - Delete the config/netbox_user tree and its netbox_user variable/wiring. - Scope terraform-infra to view/add/change/delete on the IPAM/DCIM objects it manages: prefixes, ip-addresses, ip-ranges, devices, interfaces, mac addresses.
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