checkId: check.release.environment.readiness plugin: stellaops.doctor.release severity: warn tags: [release, environment, readiness, deployment]

Environment Readiness

This check reads the Release Orchestrator’s aggregate target-readiness truth from GET /api/v1/release-orchestrator/environments/operational-truth.

What it checks

• ready: every configured target has a successful readiness evaluation.
• degraded: at least one evaluated target is not ready; Doctor returns Fail.
• not_evaluated or unavailable: readiness is unknown; Doctor returns Warn.
• empty: the environment has no deployment targets; Doctor returns Warn.
• A partial operational-truth item is never treated as healthy.

The response exposes per-environment and per-target counts. Doctor records environment_count, ready/degraded/unevaluated/empty environment counts, and target ready/not-ready/not-evaluated totals. Malformed or incompatible JSON returns Warn instead of being interpreted as an empty topology.

Diagnose

curl -s -H "Authorization: Bearer $TOKEN" \
  https://<gateway>/api/release-orchestrator/environments/operational-truth

Inspect the affected environment’s readiness.items, gate status/message, and any top-level problems. Correct missing target/agent configuration or credentials, then run the readiness validation from Release Control and re-run Doctor.

Verification

stella doctor run --check check.release.environment.readiness

Related checks

• check.release.active – in-flight deployments can stall against non-ready targets.
• check.release.rollback.readiness – reports whether production deployment history has a rollback-eligible source.
• check.release.environment.matches-approved – compares observed running digests with the approved estate.