Mechanical port to the assertion-only contract (no softened/skipped assertions): install uses live_app + generic.assert_serving (extend) + the recipe's http/playwright/api checks; upgrade seeds its data marker then generic.do_upgrade + asserts survival; backup/restore split into test_backup.py (seed->do_backup->mutate) + new test_restore.py (do_restore->assert original). Recipe-specifics preserved verbatim (keycloak realm+admin-console+kc_admin, matrix/lasuite db-service psql markers, cryptpad/n8n volume markers). No recipe now double-deploys under the deploy-once orchestrator. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
23 lines
1.0 KiB
Python
23 lines
1.0 KiB
Python
"""keycloak — 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 the marker
|
|
realm deleted after backing it up. This restores the snapshot via the shared op helper
|
|
(`generic.do_restore`, which also asserts the app is healthy + serving afterwards), then asserts the
|
|
marker realm returned (mariadb restored to the backed-up state) — the app-specific data integrity
|
|
the generic restore cannot check. Assertion-only (no deploy/teardown)."""
|
|
|
|
import os
|
|
import sys
|
|
|
|
sys.path.insert(0, os.path.join(os.path.dirname(__file__), "..", "..", "runner"))
|
|
import kc_admin # noqa: E402
|
|
from harness import generic # noqa: E402
|
|
|
|
|
|
def test_restore_returns_state(live_app, meta):
|
|
domain = live_app
|
|
generic.do_restore(domain, meta) # restore + assert healthy/serving
|
|
pw = kc_admin.admin_password(domain)
|
|
tok = kc_admin.admin_token(domain, pw)
|
|
assert kc_admin.marker_realm_exists(domain, tok), "restore did not bring back the realm"
|