mirror of
https://github.com/kevinveenbirkenbach/computer-playbook.git
synced 2026-11-08 03:38:23 +00:00
evangelostsak
1b19fe7df3
Compose app rows no longer spend deploy time on WireGuard. The full-mesh test runs on svc-net-wireguard's own row, the role deploys where its group puts it, and production keeps WireGuard for every role.
1.2 KiB
1.2 KiB
039 - svc-net-wireguard: Test Full Meshes on the Role's Own CI Row
User Story
As a maintainer, I want the full-mesh WireGuard test to run only on the role's own CI row, so that no Compose app row spends deploy time on WireGuard while every role keeps its WireGuard support in production.
Acceptance Criteria
- Compose CI rows carry no 🚇 or 🛣️ glyph and never deploy
svc-net-wireguard; thevpnaxis covers swarm rows only, as before Compose support. INFINITO_COMPOSE_VPNand its plumbing are gone.svc-net-wireguardruns on a host exactly when the host is in thesvc-net-wireguardgroup.- Outside swarm, a host in that group without a mesh is skipped with a visible message; in swarm it still fails hard.
- A role's
meta/tests.ymlcan name roles its CLI test requires undercli.requires, andtest-e2e-cliincludes them before the test runs. - The CLI test of
svc-net-wireguardrequiressys-svc-container, and the role's own deploy row runs it to green with no other application deployed. - Swarm deploys behave as before.
- Every role keeps its
networks.meshesfield and Compose hosts can still join full meshes in production.