unkinben
0287a87db7
Registering a plugin in the catalog is a distinct concern from mounting an engine, so give it its own module and config directory instead of folding sha256/command into each engine's backend module. - Add a generic 'plugin' module (vault_plugin: type/name/command/sha256/ plugin_version) that imports a binary into the catalog. - Add a config/plugins/ discovery group (filename = catalog name) and wire it through vault_cluster (plugins variable + module) and the syd1 environment. - Add config/plugins/vault-plugin-secrets-gpg.yaml pinning the released v0.1.0 binary sha256. Other engines can now register their plugin by dropping a file here; their *_secret_backend module just mounts the registered type.
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