dryrun

A dry run is a practice execution of a planned operation in which no permanent changes are made. The goal is to verify the sequence of steps, inputs, outputs, and potential errors before performing the real action.

In software and IT, dry-run mode is typically implemented as a flag or mode that causes tools to simulate actions and report what would occur. It performs validation, dependency checks, and a detailed preview of changes, allowing operators to confirm results without affecting the system.

Common usages include software deployment, configuration management, data migrations, and database schema changes. Examples in practice include Kubernetes with kubectl apply --dry-run=client (or --dry-run=server) to preview changes, Git commands with a dry-run option such as git clean -n, Terraform plan to show proposed infrastructure, and Ansible with --check to perform a safe, non-destructive run.

Advantages of dry runs include reducing risk, improving confidence before execution, and aiding debugging by exposing potential errors and misconfigurations upfront. Limitations arise because not all side effects can be fully simulated; some operations depend on runtime state or external systems, and results in a dry run may differ from a real run. Nonetheless, dry runs are a widely used precaution in development, deployment, and operational workflows.