http_fetch raced the serving layer right after backup-bot cycled the app container (served '' for a moment). Backup/restore preserve the VOLUME, so read the marker in-container via exec_in_app — correct and race-free. Serving is proven separately by install/upgrade assert_serving. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
26 lines
1.2 KiB
Python
26 lines
1.2 KiB
Python
"""custom-html — RESTORE overlay (Phase 1d, DG4): data-integrity, extends the generic restore.
|
|
|
|
Runs after the backup overlay (test_backup.py) on the SAME shared deployment, which left state
|
|
mutated to "mutated" after backing up "original". This restores the snapshot via the shared op
|
|
helper (`generic.do_restore`, which also asserts the app is healthy + serving afterwards), then
|
|
asserts the VOLUME data returned to the pre-mutation "original" — the app-specific data integrity the
|
|
generic restore cannot check. Reads the marker via exec_in_app (volume-direct, robust to the
|
|
post-restore serving race). Assertion-only (no deploy/teardown)."""
|
|
|
|
import os
|
|
import sys
|
|
|
|
sys.path.insert(0, os.path.join(os.path.dirname(__file__), "..", "..", "runner"))
|
|
from harness import generic, lifecycle # noqa: E402
|
|
|
|
MARKER_PATH = "/usr/share/nginx/html/ci-marker.txt"
|
|
|
|
|
|
def test_restore_returns_state(live_app, meta):
|
|
domain = live_app
|
|
generic.do_restore(domain, meta) # restore + assert healthy/serving
|
|
restored = lifecycle.exec_in_app(domain, ["cat", MARKER_PATH]).strip()
|
|
assert (
|
|
restored == "original"
|
|
), f"restore did not return the pre-mutation (backed-up) state: got {restored!r}"
|