unkin-agent
4f3036218d
ci/woodpecker/push/apply Pipeline was successful
The new terraform-binarylane repo provisions the BinaryLane mail gateways from Woodpecker and needs an identity, state storage, its provider token and somewhere to keep the WireGuard keypairs it generates. - add the terraform_binarylane approle and woodpecker_terraform_binarylane k8s role - add the terraform-binarylane consul role with write on infra/terraform/binarylane/ - grant the runner read on kv/service/terraform/binarylane (API token) - grant the runner create/read/update/delete on kv/service/wireguard/binarylane/* - let the agents approle seed kv/service/terraform/binarylane (no delete) Needs the terraform-binarylane woodpecker ServiceAccount in argocd-apps before CI can auth. Reviewed-on: #164 Co-authored-by: unkin-agent <unkin-agent@unkin.net> Co-committed-by: unkin-agent <unkin-agent@unkin.net>
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