unkin-agent
fc1c7121ee
Engine plugin v0.2.0 (catalog bumped in #144) added a methods field to arrstack roles, pinning a minted arrproxy key to a set of HTTP methods. Provider v0.2.0 exposes it as an optional set attribute, but the module had no input for it, so no role yaml could use it. - Bumps the vault-secrets-arrstack provider pin from 0.1.1 to 0.2.0 in root.hcl and both arrstack modules - Adds an optional methods input to arrstack_secret_backend_role and passes it through to the resource - Threads methods through the vault_cluster arrstack_secret_backend_role object type so a role yaml may carry a methods: list methods defaults to null rather than [], matching the provider's null read-back for an unrestricted role, so existing role yamls need no change and plan stays a provider-version-only diff.
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