Self-service PR-based automated Terraform
summary
Claim: a PR-based central executor runs Terraform so non‑experts can request infra changes while reviewers verify code and the actual plan output. Examples: PR-triggered terraform plan/apply via Atlantis, Terraform Cloud or env0; Atlantis runs on‑prem and provides project locking and PR comments; Terraform Cloud uses an enhanced backend and UI approvals; env0 creates ephemeral workspaces with cost limits. Notes: central executor uses a service account and needs secret injection, and Atlantis is chosen and works but requires operational upkeep.
AI-written summary · about
chapters (13)
- 0:00Self-service PR-based Terraform
- 1:16Automate Terraform workflows
- 3:43Terraform basics and state
- 8:16Breaking dev-ops divide
- 9:40Simplify complexity with modules
- 11:05Evaluating Atlantis vs Terraform Cloud
- 15:36PR workflows and CI/CD challenges
- 19:50Terraform execution and credentials
- 23:03Live demo: Atlantis
- 26:16Live demo: M0 and Terraform Cloud
- 29:24Advantages and drawbacks of PR-based workflows
- 33:17Tool selection summary
- 34:59Closing and Q&A
related talks
15mTerraform Practices: The Good, the Bad, and the Ugly
35mTerraform-Powered Platform-as-a-Service
01h 00mGotchas using Terraform in a secure delivery pipeline
30mTerraform Code Reviews: Supercharged with Conftest
55mSelf-service infrastructure is no longer a dream
31mCommodified IaC using Terraform Cloud
41mTerraform Practices - The Good, the Bad, and the Ugly
24mCreate Preview Environments for Terraform