Terraform and OpenTofu
Plan, approve and apply Terraform or OpenTofu roots as a deployment.
At a glance
Section titled “At a glance”| Category | Infrastructure as code |
| Authentication | Backend credentials via workload identity or secrets |
| Provider id | terraform |
What it does
Section titled “What it does”- Plan output attached to the deployment
- Manual approval gate between plan and apply
- Drift check on a schedule
Set up
Section titled “Set up”- Install
terraformortofuon the runner pool (or use the provided image). - Create an Infrastructure of kind
terraformand set the working directory and workspace. - Give the runner identity access to the state backend and target accounts.
- Add a manual gate so a human reviews the plan before apply.
Configuration
Section titled “Configuration”Illustrative configuration. Non-secret settings are stored as integration config; credentials are stored as encrypted Slipway secrets and referenced by name.
infrastructure: kind: terraform config: tool: opentofu # terraform | opentofu working_dir: infra/prod workspace: prod var_files: [prod.tfvars]Related
Section titled “Related”- Integrations overview
- Secrets for how credentials are stored and masked
- Webhooks and events for the events integrations subscribe to