A green plan is evidence, not proof. Build the pyramid: lint in seconds, policy on every PR, real-cloud verification only where shared modules and money justify the burn.
an account raises the per-topic limit · no card
← Infrastructure as Code & Configuration / 15
hardNewGitLabAtlassianNetflix
Design the CI checks for a Terraform repository. What runs at each stage, and what can each check never catch?
A green plan is evidence, not proof. Build the pyramid: lint in seconds, policy on every PR, real-cloud verification only where shared modules and money justify the burn.
Updated Sep 2026 · Grounded in researched DevOps, SRE and platform engineering interview loops, written to a senior-engineer editorial bar, and never padded to hit a word count.
UP NEXT ON YOUR JOURNEY
Next in this trackA routine change wants to replace a production resource. How do Terraform updates become replacements, and what controls that?Next in this trackAn apply planned to destroy and recreate the production database. Which lifecycle arguments belonged on that resource?Next in this trackA module needs an AMI ID and three subnet IDs. Do you hardcode them, accept variables, or look them up?
DISCUSSION · 0
Nothing here yet. Say how you would answer it.