docs(720): name all three Komodo stacks and the label-based resolution rule
PR Gates / CI image pin matches docker/ci (pull_request) Successful in 26s
PR Gates / decisions lifecycle (pull_request) Successful in 33s
PR Gates / Docs update reminder (pull_request) Successful in 31s
review-verdict/h10 Exempt: docs-only change (no code, no protected path)
Review verdict / Set review-verdict status (pull_request_target) Successful in 10s
PR Gates / Script tests (pytest) (pull_request) Successful in 2m31s
Build ErsatzTV Image / Build & test (.NET) (pull_request) Successful in 12s
Build ErsatzTV Image / EF migration integrity (SQLite + MySql) (pull_request) Successful in 10s
Build ErsatzTV Image / Build & push image (amd64) (pull_request) Skipped
Build ErsatzTV Image / Functional E2E (curl + UI contracts) (pull_request) Successful in 10s
Build ErsatzTV Image / API docs in sync (OpenAPI + endpoint index) (pull_request) Successful in 10s
Build ErsatzTV Image / Formatting (changed .cs conform to .editorconfig) (pull_request) Successful in 7s

A live Komodo stack literally named `ersatztv` exists, but it owns the
TEST channel (`ersatztv-test`, tracks `:latest`, auto_update true) — not
prod. `DeployStack ersatztv` succeeds and looks healthy while promoting
nothing. Extend the existing jazz-media/media-servers callout with this
third stack and the rule that resolves the trap: identify the prod stack
by the container's `com.docker.compose.project.config_files` label, not
by stack name. Verified live against jazz (192.168.1.29) on 2026-08-11.

fixes #720
This commit is contained in:
2026-08-11 18:58:27 +02:00
parent 884ac8a7e9
commit d9c80e2a49
+15
View File
@@ -114,6 +114,21 @@ commit in the range (see the `decisions.md` header) — routine lifecycle metada
> `DeployStack media-servers` silently targets the **dead** stack. Confirm with
> `/read ListStacks` before deploying.
>
> **A third stack, literally named `ersatztv`, is also live and is NOT prod** (verified 2026-08-11):
> it owns `ersatztv-test`, tracks the floating `:latest` tag, and runs with `auto_update: true`.
> `DeployStack ersatztv` succeeds and looks healthy — it just promotes nothing to prod. Three names,
> one target:
>
> | Stack name | project_name | auto_update | owns |
> |---|---|---|---|
> | `jazz-media` | `media-servers` | `false` | `ersatztv` (**prod**, tracks `:prod`) |
> | `ersatztv` | `ersatztv` | `true` | `ersatztv-test` (tracks `:latest`) |
> | `media-servers` | — | — | dead stack on bumblebee, `unhealthy` |
>
> Don't resolve the prod stack by name at all — resolve it by the **container's**
> `com.docker.compose.project.config_files` label (e.g. via `docker inspect`), which points at the
> actual compose file path and can't be confused by a same-named stack.
>
> **There is no Global Auto Update fallback anymore**: `jazz-media` has `auto_update: false`
> (`poll_for_updates: true` only), so nothing promotes `:prod` on a timer — promotion is manual,
> full stop. The old "don't cut a tag near the 03:00 run" caveat no longer applies.