> ## Documentation Index
> Fetch the complete documentation index at: https://kvm.xdr.ooo/llms.txt
> Use this file to discover all available pages before exploring further.

# DRY_RUN & Validation

> Use DRY_RUN and Full Configuration Validation to inspect a deployment before making system changes.

# DRY\_RUN & Validation

The installer family is designed to make host changes visible before execution.

## DRY\_RUN

DRY\_RUN defaults to enabled.

When `DRY_RUN=1`:

* commands are displayed rather than executed
* the operator still sees the normal confirmation flow
* destructive/system-changing commands are not executed
* the workflow can be inspected in the same step order as real execution

> [!WARNING]
>
> DRY\_RUN is not a substitute for reviewing the target host. It helps expose intended changes but cannot prove that every production dependency will behave identically.

## Full Configuration Validation

Validation is read-only and checks the active environment and configuration. The common result model is:

* **OK** — requirement satisfied
* **WARN** — review or recommendation
* **FAIL** — blocking problem

A FAIL must be corrected before deployment.

## Recommended gate

**1. Run with DRY\_RUN enabled**

Walk through the selected installer and verify detected NICs, disks, versions, image inputs and VM parameters.

**2. Run Full Configuration Validation**

Resolve every blocking result and review warnings.

**3. Confirm recovery access**

Ensure console/out-of-band access and rollback or recovery procedures are available.

**4. Disable DRY\_RUN only for the approved execution**

Re-check the configuration summary before confirming system-changing steps.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.