checkId: check.release.configuration plugin: stellaops.doctor.release severity: removed tags: [release, configuration, workflow, validation]

Release Configuration (REMOVED)

This Doctor check was removed on 2026-07-12 (sprint SPRINT_20260713_002, task BL-6). It no longer runs and no longer appears in stella doctor output. This article is retained only to explain the removal for operators who have older runbook links.

Why it was removed

The check GET-ed the Release Orchestrator at /api/v1/workflows and validated a “release workflow definition” data model – stages, stage transitions, entry points, and per-stage environment mappings.

The Release Orchestrator never implemented that surface:

• There is no /api/v1/workflows handler in the Release Orchestrator. The only thing behind that path is a dead gateway ReverseProxy route stub that forwards to a service endpoint which does not exist, so every request 404s.
• The Release Orchestrator’s baseline schema has no “workflow” table and no workflow-definition entity. Its domain models releases (Draft -> Ready -> Promote -> Deploy -> Rollback) and environments, not a stage graph.
• The stella release workflow list/show/edit/create/validate commands referenced by the old version of this article do not exist in the CLI.

Because the endpoint always 404s, the check degraded to a permanent Warnthat could never Pass – a health check that reports a problem regardless of system state. Unlike its sibling release checks (which target real Release Orchestrator concepts, even if some use a stale path), this check had no real endpoint to re-point at, so it was dropped rather than rewritten.

What to use instead

The remaining stellaops.doctor.release checks cover the concepts the Release Orchestrator actually exposes:

• check.release.active – health of in-flight releases.
• check.release.environment.readiness – target environments exist and are reachable/healthy.
• check.release.promotion.gates – promotion gate configuration.
• check.release.rollback.readiness – rollback capability per environment.
• check.release.environment.matches-approved – running estate matches approved releases (drift).

The former check.release.schedule was also removed because Release Orchestrator has no schedule executor or schedule read model; see its removal note.