mirror of
https://github.com/kevinveenbirkenbach/computer-playbook.git
synced 2026-11-06 02:54:26 +00:00
kevinveenbirkenbachandClaude Opus 5
3d93c81f70
The split left the swarm track without any teardown: a `base swarm` run started the development stack in base/04_bootstrap.sh and never brought it down, so it leaked AppArmor, dev DNS and IPv6 state onto the host and ran the swarm cluster alongside a live dev stack the old suite had already released. The old single job ran `make compose-down` + `make environment-teardown` as step 10, immediately before 12_swarm.sh and 13_roundtrip.sh. The swarm track now reproduces exactly that: 01_teardown releases the stack before 02_zombie and 03_roundtrip (which are byte-identical to the old steps apart from their source path), and 04_teardown leaves the host clean — something the old suite never did, since it ended on the roundtrip's restarted stack. Both closing steps and the new leading one share utils/teardown.sh so the teardown cannot drift between tracks. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
9 lines
367 B
Bash
Executable File
9 lines
367 B
Bash
Executable File
#!/usr/bin/env bash
|
|
# Release the development stack the base track started, so the swarm cluster
|
|
# runs alone. The swarm steps only need the node image on the host daemon,
|
|
# which 03_build.sh put there and `make compose-down` does not touch.
|
|
set -euo pipefail
|
|
|
|
SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
|
|
exec bash "${SCRIPT_DIR}/../utils/teardown.sh"
|