93b0d79998
Rename the stack and script accordingly:
- test-restart-hook stack → test-restart
- test-restart-hook-multi stack → test-restart-multi
- run-restart-hook-test.sh → run-restart-test.sh
- start-hook-marker file → marker
- pod-repo dirs test-restart-hook-pod-{a,b} → test-restart-pod-{a,b}
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
||
|---|---|---|
| .. | ||
| README.md | ||
| stack.yml | ||
README.md
test-restart-multi
E2E test stack used by tests/k8s-deploy/run-restart-test.sh to cover the
multi-repo case: pods: references two pod repos, each shipping its own
deploy/commands.py. deploy create should produce
<deployment>/hooks/commands_0.py and <deployment>/hooks/commands_1.py,
and deployment start should invoke both start() hooks (each writes its
own marker file so neither overwrites the other).
The pod repos themselves are created by the test script as bare-repo +
working-clone pairs under $CERC_REPO_BASE_DIR/test-restart-pod-{a,b};
they are not committed to this repository. Each pod repo ships its own
docker-compose.yml (resolved by get_pod_file_path for dict-form pods)
and stack/deploy/commands.py — the stack repo only owns stack.yml.