Skip to content

Use an Auditable Blueprint Preflight Bypass

  • Purpose: Represent an exceptional recovery decision as run evidence instead of hidden validation drift.
  • Owner: Platform operations
  • Impact: Allows execution after blueprint preflight is bypassed. Contract and structural validation still apply.
  • Rollback strategy: Stop the run, correct the failed prerequisite, and return to normal preflight execution.

Pre-checks

Run preflight and retain the reported failure:

ENV=<environment>
REF=<blueprint-ref>
hyops blueprint preflight --env "$ENV" --ref "$REF"

Use a bypass only when the failure is understood, the recovery has an owner, and proceeding is safer than leaving the environment unchanged.

Execute

Supply both required flags and use a concise, specific reason:

hyops blueprint deploy \
  --env "$ENV" \
  --ref "$REF" \
  --execute \
  --skip-preflight \
  --preflight-bypass-reason "controlled recovery for <condition>"

The reason must be a single printable line. A reason without --skip-preflight, or a bypass without a reason, is rejected.

Verify

Confirm the operation completed and then run preflight again without a bypass:

hyops blueprint preflight --env "$ENV" --ref "$REF"

Records

The blueprint run record stores the preflight decision, status, and reason. Record the original failure and the corrective action in the incident or change record.

Rollback

If execution fails, use the blueprint's normal retained-resource or destroy path. Do not repeat the bypass until the new failure has been assessed.

References