4 Commits

Include renames

Author	SHA1	Message	Date
bvandeusenandClaude Opus 5.5	4c546a9c4d	test(backup): run 9076's three failures (#5673, #5674) ... - The audit-wording guard now reads both branches of a conditional action ("backup.made" if ok else "backup.failed"), and its self-test covers that. - The Backups save test no longer asserts the session's tz, which sign-in state sets, not the test. - The restore integration test uses the app's own metadata. all_metadata without plugin dirs imports the `plugins` package as the tests do; loading by path under the loader's names is only for `steward restore`. Loading by path in the shared test process had mapped traefik and unifi tables a second time for later tests. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-12 07:27:24 -04:00
bvandeusenandClaude Opus 5.5	357bb6480d	fix(backup): restore finds plugin tables by path, as the app loads them (#5674) ... Run 9075: the restore got through schema and data, then all_metadata's `import plugins` failed in the image, where plugins/ is a directory the app loads by path (PLUGIN_DIRS), not an installed package. It now loads each plugin under the loader's own module name from the bootstrap's plugin dirs, which `steward restore` passes. A plugin whose models are already mapped under either name is skipped rather than mapped twice. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-12 07:23:58 -04:00
bvandeusenandClaude Opus 5.5	fe51451704	fix(backup): restore through psql, dropping pg_restore 17's transaction_timeout line (#5674) ... Run 9074's smoke restore stopped at "SET transaction_timeout = 0": pg_restore 17 sends it, and the Postgres 16 server doesn't know the setting. Each section is now written as a script (pg_restore --file=-), that one line is dropped, and psql -v ON_ERROR_STOP=1 runs the rest, so any other error still stops the restore. If psql stops, pg_restore is killed rather than left blocked on its pipe. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-12 07:19:54 -04:00
bvandeusenandClaude Opus 5.5	b875160c40	feat(backup): steward backup and steward restore; CI restores a dump and boots on it (#5672, #5674) ... The backup file (#5672 "Backup file: pg_dump of config + audit + alert history, the secret key and a manifest"): steward-<UTC>.tar holding a pg_dump --format=custom with metrics', check results' and Docker/Traefik/ UniFi rows left out, the secret key, and a manifest. Every table is named KEPT or EXCLUDED in steward/backup/contents.py, and a guard test fails on a new one. The image gains postgresql-client-17 (approved, System 180). The restore (#5674 "Restore: `steward restore` and a CI test that a dump brings Steward back"): pg_restore in its three sections. Between data and constraints, a kept row pointing at a left-out row gets what its foreign key's ON DELETE says (alert_events.ansible_run_id is cleared). It refuses a non-empty database unless --wipe, and puts the backup's key in /data/secret.key. Migrations run on Steward's next start. `steward` stays the server command: it is now a click group that serves when given no subcommand. The publish smoke step backs up the booted image's database, restores it into a second one, checks a marker setting came back and plugin_metrics is empty, and starts Steward on it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-12 07:14:04 -04:00