Plan review & drift

Review a narrow release change

Lesson 5 of 20 · 12 min · Module 2: Review change and scope access

Inspect the difference before changing an operating environment.

Start this lesson →

Free. No installation: you write and run the code in your browser, and it is checked automatically.

By the end, you’ll be able to…

  • State which difference is intended
  • Read before and after

The idea

Terraform accepts .tf.json as an alternative configuration representation. Here, built-in terraform_data values make state and plan concepts inspectable without provisioning a cloud resource.

01State which difference is intended

The release changes image identity. Replica count is an unrelated setting that should remain stable during this exercise.

02Read before and after

The plan includes the old and new values. Review the actual diff rather than approving a change just because it is called an update.

03Distinguish desired changes from drift

Drift is a difference between recorded or observed state and configuration. Decide deliberately which source should be authoritative for the repair.

Your turn

Recorded app state is image notes:1.0 and replicas 2. Set image to notes:2.0 while preserving replicas 2. The practice plan must update only terraform_data.app.

What the checks look for

  • Updates one resource
  • Changes image while preserving scale
Try it in the editor →

Take this with you

Review the proposed operational change, not just the configuration diff.

Go a little further

Explain why an unexpected delete in a release plan should stop the review.

Learn Infrastructure & Operations for free

20 short lessons with real code and instant checks.

See the whole course →