Delivery for Terraforms
Delivery for Terraform is how infrastructure changes move through CI/CD safely. A typical pipeline runs format, validate and security checks on a pull request, posts the plan for review, and applies the approved plan after merge. Credentials come from short-lived identities rather than stored keys, and apply steps are serialised to protect state.
Stage: Teams and Operations · Part of the Terraform roadmap · Last reviewed 19 November 2026
What to learn in Delivery
- Build a pull request pipeline that runs checks and posts the plan
- Apply a saved plan file so what was reviewed is what runs
- Authenticate to the cloud with OIDC instead of long-lived access keys
- Require manual approval before applying to production
- Detect configuration drift on a schedule and report it
Delivery interview questions
Why apply a saved plan in a pipeline?
Running terraform plan -out saves exactly what was proposed, and apply of that file executes only those changes. If you re-plan at apply time, infrastructure or code may have changed since review, so the result could differ from what the reviewer approved.
Why avoid long-lived cloud access keys in CI?
Static keys stored as secrets can leak and rarely get rotated. Using OIDC federation or similar lets the pipeline request short-lived credentials tied to the repository and branch, reducing the damage from a leak and removing the need to manage secrets.
Where Delivery fits in the Terraform roadmap
Delivery belongs to the Teams and Operations stage (advanced level). Collaborate.
Other units in this stage
Back to the full Terraform roadmap