Patterns icon
Pattern guide

Dry Run

Preview planned actions without applying changes.

Intent

Let operators inspect what will change before execution.

When to use

  • Changes are destructive or high risk.
  • Large syncs need preview.
  • Stakeholders want to review planned actions.

Core mechanics

  • Generate an action plan without applying changes.
  • Report counts and sample records.
  • Require explicit apply to proceed.

Implementation checklist

  1. Implement a simulation path for each action.
  2. Output a detailed plan with counts.
  3. Highlight risky or destructive steps.
  4. Document differences between dry-run and apply.
  5. Store the plan for review.

Failure modes and mitigations

  • Drift between dry-run and apply -> recompute before execution.
  • False confidence -> document limitations and assumptions.
  • Incomplete preview -> ensure all actions are listed.

Observability and validation

  • Planned vs applied counts.
  • Review notes and approvals.

Artifacts

  • Dry-run report.
  • Action plan export.
Seen in production

Seen in production as

Atlas project

google-classroom-guardians

Manage Google Classroom guardian relationships by reading a CSV of students and guardians, computing required invitations/removals, and …

Related

Related patterns