DEV Community

Honey Kiran
Honey Kiran

Posted on Originally published at honeykiran.substack.com on

The Plan Was Green. The Apply Disagreed.

The Plan Was Green. The Apply Disagreed.

A thread on r/Terraform this week walks through a familiar ceremony: the plan comes back clean, the reviewers nod at the diff, the apply runs — and the infrastructure that lands is not the infrastructure the plan described. (The thread is one team's report; the gap it names lives in every pipeline that treats the plan as the promise.)

WHY PLANS LIE WITHOUT LYING

A plan is a photograph taken at a moment, of a world that does not hold still. Between the plan and the apply: someone else's pipeline lands a change, a data source re-reads a value that moved, a provider resolves a default differently than the plan assumed, state drifts because a human fixed something by hand at 2 AM and told no one. The plan was accurate. It was accurate about a world that no longer exists.

Then there is the quieter gap: the plan shows what Terraform intends to send. Providers translate. Defaults expand. A resource that planned as an in-place update applies as a replacement because the API underneath never supported the in-place path. The diff you approved was real — it was just written in a language one layer above the one that executes.

THE CULTURE MAKES IT WORSE

Review culture trains the eye on the plan: it is the artifact in the PR, the thing the approval button sits under. Nobody's approval button sits under the apply log. So the organization gets very good at reading plans and very casual about reading what the apply actually did — the verification step quietly became "the apply exited zero."

Exiting zero means the commands ran. It does not mean the world matches the photograph.

CLOSE THE GAP

  1. Apply from the saved plan, in the same run. The reviewed plan file is the thing applied — never a fresh plan generated at apply time and waved through.

  2. Refresh immediately before. A plan older than the pipeline that produced it is a rumour. Refresh, re-plan, and if the diff moves, the approval resets.

  3. Read the apply like a reviewer. The post-apply state diff — what exists now versus what the plan promised — is a first-class artifact. File it next to the plan.

  4. Alarm on replacement. Any resource the plan called an update and the apply replaced is a named event, reviewed by a human, every time.

Sources

r/Terraform discussion thread, November 2026 (one team's report; the plan/apply mechanics are standard Terraform behaviour).

Question for you: pull your last production apply and compare its result against the plan that was approved — how many lines differ, and who in your pipeline is assigned to notice?


Disclaimer

  • This post describes my personal experience with my own systems and accounts, in my own words. It is a first-person account of what I observed and what I do in my own work — not a statement of any company’s intentions, policies, or internal decisions. Where I do not know something, the post says so.

  • I am not affiliated with, endorsed by, or speaking for any company, product, or vendor named in this post. All product and company names are trademarks of their respective owners and are mentioned only to describe the experience accurately.

  • Any error messages, documentation excerpts, or figures quoted here are reproduced from my own records or from the public sources linked in the post, believed accurate at the time of writing. Product behavior changes over time; verify against current official documentation before relying on any detail.

  • Nothing in this post is professional, financial, legal, or security advice for your specific situation. Examples are illustrative — validate in your own environment before running anything in production.

  • Corrections are welcome. If any company named here publishes an official statement, or if any detail is wrong, I will update this post and note the correction. The goal is an accurate public record, not a verdict.


© 2026 Honey Kiran. All rights reserved.

Honey Kiran · DevOps & Platform Engineering

AI agents transforming DevOps, infra, platform, security & SRE. The shift nobody works anymore: deep dives, 3AM Files, and OpsBites.

Examples are illustrative — validate in your own environment before running in production.

Top comments (0)