0 Fork 0

mirror of https://github.com/kevinveenbirkenbach/computer-playbook.git synced 2026-11-09 20:26:33 +00:00

Files

T

kevinveenbirkenbachandClaude Opus 4.8 baae3c377e fix(openresty-swarm): out-of-band overlay creation + stop-first host-mode redeploy

- Load openresty via the sys-svc-compose network/routine.yml helper (same
  pattern as the db/ollama roles) so the shared `openresty` overlay is created
  attachable + swarm-scoped before the stack deploys; emit the top-level
  networks block via compose_networks.
- Add an opt-in `order:` to the swarm update_config and set it to `stop-first`
  for openresty: it publishes 80/443 in host mode, so a default rolling update
  deadlocks (the new task cannot bind ports the old task still holds).
- Relax the network-include lint to accept a single compose_networks lookup in
  a host-mode template (openresty is mode-conditional: host in compose, overlay
  in swarm).
- Whitelist openresty's path_join network/routine.yml include in
  .ansible-lint-ignore (same dynamic-include pattern as the db/ollama roles).

Runtime-confirmed (swarm, attempt 32): openresty created its overlay, attached
consumers, reached backends, and redeployed cleanly.

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

2026-06-17 19:49:18 +02:00

__init__.py

…

README.md

…

test_compose_templates.py

fix(openresty-swarm): out-of-band overlay creation + stop-first host-mode redeploy

2026-06-17 19:49:18 +02:00

test_images_configuration.py

refactor(tests): regroup meta tests, add native-metrics contract

2026-05-17 12:50:35 +02:00

test_no_raw_docker.py

refactor(svc-db-mariadb, web-app-decidim): migrate docker_container_exec to container wrapper + extract SQL

2026-05-19 00:39:36 +02:00

test_services_image_version_valid.py

…

README.md

Docker Tests 🐳

Integration tests that validate Docker-level contracts for role services: compose template includes, declared service keys, and image/version validity.

Tests in this directory MUST only cover Docker-specific semantics (images, tags, compose-service configuration). Generic compose-structure rules MUST live under tests/integration/compose/, and backup-related checks MUST live under tests/integration/backups/.

For framework, directory layout, and make test-integration usage see integration.md.