Use Dry-Run Mode
Dry-run mode lets you see exactly what the adapter would create or update without touching the Omnia cluster. This is useful for reviewing changes before applying them, testing configuration, and CI validation pipelines.
Enable dry-run
Section titled “Enable dry-run”Set dry_run: true in your deploy configuration:
deploy: provider: omnia config: api_endpoint: "https://omnia.example.com" workspace: "my-workspace" providers: default: claude-prod dry_run: trueWhat happens in dry-run mode
Section titled “What happens in dry-run mode”When dry_run is true, the Apply operation:
- Parses and validates the pack JSON and deploy configuration.
- Generates the full list of desired resources (identical to a real apply).
- Streams progress events for each resource with
plannedstatus. - Returns adapter state with all resources marked as
planned. - Makes zero API calls to the Omnia cluster.
No authentication is required for the dry-run itself — the adapter does not create an HTTP client. However, the configuration is still validated, so api_endpoint, workspace, and providers must be set.
Dry-run output
Section titled “Dry-run output”Each resource appears in the progress stream:
Planned configmap: my-pack-packdataPlanned prompt_pack: my-packPlanned tool_registry: my-pack-toolsPlanned agent_runtime: my-packThe returned state contains the same resource entries, each with "status": "planned".
Plan vs dry-run
Section titled “Plan vs dry-run”Both plan and dry-run apply preview resources, but they serve different purposes:
| Plan | Dry-run Apply | |
|---|---|---|
| Purpose | Show what would change | Simulate the full apply workflow |
| API calls | None | None |
| Prior state diff | Yes — shows create/update/delete | No — always shows create |
| Progress events | No | Yes — streams resource events |
| State output | Change list | Full adapter state (with planned status) |
Use plan to review diffs against an existing deployment. Use dry-run apply to validate the complete apply workflow end-to-end without side effects.
CI usage
Section titled “CI usage”Dry-run is useful in CI pipelines to validate that a pack compiles and produces valid deploy resources:
# Validate the pack produces a valid deployment planpromptarena deploy apply --dry-runThe command exits with code 0 if the pack and configuration are valid, and non-zero if parsing or validation fails.