From f9f8f65cee87109183c8253b3e5409831cfa10fe Mon Sep 17 00:00:00 2001 From: Timothy Date: Tue, 11 Aug 2026 19:26:07 +0000 Subject: [PATCH] docs(720): name all three Komodo stacks and the label-based resolution rule (#769) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit A live Komodo stack literally named `ersatztv` owns the TEST channel, not prod. `DeployStack ersatztv` succeeds, looks healthy, and promotes nothing — silent and plausible. Extends the existing callout with all three stack names and the resolution rule: identify the prod stack by the container's `com.docker.compose.project.config_files` label, not by stack name. Container labels re-verified live on jazz 2026-08-11; the verification date is scoped to what was actually re-measured, after review flagged the stamp as covering unchecked values. The server-management half (the `komodo` skill still uses the dead `media-servers` as its worked deploy target) cannot land in this repo and is tracked as server-management#743. #720's box 2 was re-scoped to that hand-off rather than ticked as though the skill were fixed. fixes #720 Co-authored-by: Timothy --- docs/ci-cd.md | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/docs/ci-cd.md b/docs/ci-cd.md index 3bc241a9f..ccc0f69f7 100644 --- a/docs/ci-cd.md +++ b/docs/ci-cd.md @@ -114,6 +114,24 @@ 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**: it owns +> `ersatztv-test`, tracks the floating `:latest` tag, and runs with `auto_update: true`. (Stack +> name, compose project, config-file path and image tag re-confirmed from the container labels on +> jazz 2026-08-11; the `auto_update` flags and the bumblebee `unhealthy` status are carried from +> the earlier checks noted above, not re-measured that day.) +> `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.