A plan summary can show one add and one destroy for a single resource replacement. Before approving it, locate the resource address, find the attribute driving the replacement, and determine what depends on the old instance.

sh
terraform plan -out=tfplan
terraform show -no-color tfplan

Review in order of impact

  • Check the account, region, workspace, and input values before interpreting the diff.
  • Read destroy and replacement actions first. Ask what changes if the old instance disappears before the new one is ready.
  • Review changes to routes, permissions, and retention settings even when the resources stay in place. A small diff can affect many callers.

A saved plan lets you apply the selected changes rather than recomputing a different plan at approval time. If someone changes state or the environment materially between review and apply, refresh the plan and review again. Keep the saved artifact in restricted storage because it can contain sensitive values.

Treat drift as information

If a resource changed outside Terraform, determine whether the live setting is an emergency correction that should be adopted or an unintended change that should be reverted. Write down that decision in the same review. Otherwise the next apply can silently undo a fix whose purpose was never recorded.

References