Ben Vincent
14790f8277
- import pki, ssh, kv, rundeck engines - deploy all roles from terraform - deploy all policies from terraform - deploy all approles from terraform
38 lines
1.1 KiB
Markdown
38 lines
1.1 KiB
Markdown
# terraform-vault
|
|
|
|
A repository to manage the configuration of Vault secret engines, authentication modes and policies.
|
|
|
|
|
|
# Usage
|
|
|
|
1. Initialize Terraform
|
|
|
|
Once you have your backend block configured, you need to initialize your Terraform working directory to configure the backend:
|
|
|
|
```bash
|
|
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.
|
|
|
|
2. 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.
|
|
|
|
3. Example Consul KV Structure
|
|
|
|
In Consul, the state file will be stored in the KV store under the specified path:
|
|
|
|
```bash
|
|
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:
|
|
|
|
```bash
|
|
consul kv get terraform/state
|
|
```
|