0 Fork 0

mirror of https://github.com/kevinveenbirkenbach/computer-playbook.git synced 2026-11-11 21:26:44 +00:00

Files

T

kevinveenbirkenbachandClaude Opus 5 ac5b879b85 fix(swarm): resolve the deployment mode a stack was actually deployed with

d130f5559 moved the swarm converge wait onto compose_mode_force-or-
DEPLOYMENT_MODE and left the compose health wait beside it reading
DEPLOYMENT_MODE raw. A role pinned with compose_mode_force: compose on a
swarm cluster then satisfied neither condition - the compose branch saw
'swarm' and the swarm branch saw 'compose' - so it got no post-deploy
readiness wait at all. web-app-matrix in its ansible flavour is the live
case.

The database lookup read DEPLOYMENT_MODE raw for the same reason, handing a
pinned role a swarm service name and a resolve-container-id address for a
stack that docker compose had created.

The override is scoped to the dedicated database only. A dedicated engine
runs inside the consumer's own stack, so the consumer's pin governs it; a
central engine is its own stack under the cluster mode, and letting a
consumer's pin reach it would rename a service swarm really did create.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

2026-08-18 05:21:54 +02:00

cli

fix(ci): make the failed-run retrigger reach its dispatch

2026-08-18 05:21:52 +02:00

library

…

plugins

fix(swarm): resolve the deployment mode a stack was actually deployed with

2026-08-18 05:21:54 +02:00

roles

fix(test): take the project root from the package, not from parents[5]

2026-08-18 03:22:05 +02:00