Promote the same code version, then generate and approve a separate saved plan against each environment's state and inputs. Pin, apply each reviewed artifact in sequence, and let the gates rise as you approach production. Environment branches quietly undo all of it.
← Infrastructure as Code & Configuration / 28
mediumNewAccentureSalesforceFlipkart
App teams promote builds from dev to staging to production. How should promotion work for infrastructure changes?
Promote the same code version, then generate and approve a separate saved plan against each environment's state and inputs. Pin, apply each reviewed artifact in sequence, and let the gates rise as you approach production. Environment branches quietly undo all of it.
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.
20 answers per topic instead of 10, and your progress kept · no cardor unlock all 390 remaining answers · ₹2,000 / $25
UP NEXT ON YOUR JOURNEY
Next in this trackA major provider release lands and forty stacks pin the old version. How do you roll the upgrade forward without a fortnight of fire drills?Next in this trackA single Terraform apply takes four hours and keeps hitting cloud API rate limits. What is actually broken, and what do you fix first?Next in this trackProduct wants a full environment per pull request. How do you build ephemeral Terraform previews that do not torch the budget?
DISCUSSION · 0
Nothing here yet. Say how you would answer it.