unkinben
13c1f5c1ba
Why: after the engine is first configured, rotate-root changes the live admin password so it diverges from the KV seed. Re-reading the (possibly stale) seed on a later apply must not push it back and clobber the rotated password. Ben asked that the seed be used only when initially creating the config. Change: - Add lifecycle ignore_changes on admin_username/admin_password to the gitea_secret_backend resource, making the module create-only for the seeded credential. Noted inline that the rancher/litellm seed modules lack this. Claude-Session: https://claude.ai/code/session_015ur3i7D2azsMAWTSVABApv
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