3 Commits

Include renames

Author	SHA1	Message	Date
bvandeusenandClaude Opus 5.5	bd762307e0	feat(prometheus): the widget template library: list, edit with live preview, paste in, upload, export, duplicate (#5692) ... Prometheus gains a "Widget templates" tab beside Targets. It lists the built-in templates and an admin's own, any that no longer pass the checker first. A template opens as its YAML beside a live preview drawn over a chosen target exactly as the dashboard widget draws it (routes.draw, now shared by both). An admin writes or pastes a new one, reads a .yaml upload into the editor to look over, duplicates any template under a free name, edits and deletes their own; anyone can export the YAML. Built-in templates are read-only. Custom templates are rows in prometheus_widget_templates (migration prometheus_002_templates), kept in backups, keyed "custom:<id>" so a rename keeps its widgets. Saving needs a template that passes the checker and a name no other template has. Create, update and delete are audited and link to the template. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-14 09:22:31 -04:00
bvandeusenandClaude Opus 5.5	f1f2cb02cc	fix(backup): name ansible_target_groups (kept) and email_outbox_events (left out) (#5672) ... The guard in tests/core/test_backup_contents.py caught both on run 9073. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-12 07:16:04 -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