checkId: check.release.rollback.readiness plugin: stellaops.doctor.release severity: warn tags: [release, rollback, disaster-recovery, production]
Rollback Readiness
Rollback is deployment-specific in Release Orchestrator. This check therefore uses the real environment and deployment contracts rather than the removed /api/v1/environments/rollback-status shape.
What it checks
- Lists environments from
GET /api/v1/release-orchestrator/environmentsand keeps environments whose authoritativeisProductionflag is true. - Lists the 20 most recent deployments for each production environment through
GET /api/v1/release-orchestrator/deployments?environment=<id>&pageSize=20. - Reads deployment details and uses the authoritative
canRollbackaction flag.
The check passes when each production environment has a recent rollback-eligible deployment, warns when an environment has no deployment history, and fails when its recent history contains no rollback-eligible deployment. It does not invent environment-level health-probe or migration-reversibility fields that the API does not provide.
Diagnose
stella deployment list --environment <environment-id> --page-size 20 --json
stella deployment show <deployment-id> --json
stella deployment show exposes canRollback and the available actions. An authorized operator can start the rollback from Release Control or the corresponding POST /api/v1/release-orchestrator/deployments/<deployment-id>/rollback endpoint after reviewing the target versions and blast radius.
Verification
stella doctor run --check check.release.rollback.readiness
Related checks
check.release.active– detects stuck or failed in-flight deployments.check.release.environment.readiness– verifies target readiness separately.check.release.environment.matches-approved– detects drift from the approved deployed estate.
