(feature) Improve retention UX and prune safety #14

parkel · 2026-05-21T01:27:11+02:00

parkel commented

2026-05-21 01:27:11 +02:00

Summary

Make retention plans explain why snapshots are kept or selected for deletion.
Surface scheduled prune limit warnings on dashboard, host detail, run detail, and retention plan.
Show base protection behavior and base-of reasons in the retention plan.
Make manual retention apply safer by requiring host and delete-count confirmation.
Surface incomplete snapshots as operator warnings without deleting them automatically.
Preserve scheduled backup warning status when post-backup pruning fails.

## Summary - Make retention plans explain why snapshots are kept or selected for deletion. - Surface scheduled prune limit warnings on dashboard, host detail, run detail, and retention plan. - Show base protection behavior and base-of reasons in the retention plan. - Make manual retention apply safer by requiring host and delete-count confirmation. - Surface incomplete snapshots as operator warnings without deleting them automatically. - Preserve scheduled backup warning status when post-backup pruning fails.

parkel added 5 commits 2026-05-21 01:27:12 +02:00

(ui) Make retention planning warnings explicit 50eb7cf2f3

Show keep/delete reasons in the retention plan, surface scheduled prune
limit warnings, and explain base snapshot protection before retention is
applied.

Also surface incomplete snapshots from the retention views without deleting
them automatically, so interrupted backups are visible on the dashboard,
host detail, and retention plan.

(ui) Surface retention warnings on run detail 90e293facd

Show host-level retention warnings on run detail pages so successful or
warning runs still expose scheduled prune limit issues and incomplete
snapshots that need operator attention.

(feature) Require delete count confirmation for retention apply f76b6cad14

Make manual retention application more explicit by requiring operators to
confirm both the host name and the current number of planned deletions.

This reduces the risk of applying a stale or misunderstood retention plan
when the delete set changes between review and confirmation.

(bugfix) Preserve scheduled backup warning status 994f7f66c4

Update the scheduler to reflect the actual scheduled BackupRun status after
a run completes, so prune warnings are shown as schedule warnings instead
of being reported as successful schedule executions.

(ui) Show retention apply details on run detail 97753c3d3c

Record planned delete counts, max-delete settings, base protection, and
ignored incomplete snapshots in retention apply results.

Surface those details on run detail pages so scheduled and manual prune
outcomes are understandable without reading the raw JSON payload.

parkel merged commit 17215fd191 into master

2026-05-21 01:27:20 +02:00

parkel deleted branch issue-4-retention-ux-and-safety

2026-05-21 01:27:20 +02:00

parkel referenced this issue from a commit

2026-05-21 01:27:20 +02:00

Merge pull request '(feature) Improve retention UX and prune safety' (#14) from issue-4-retention-ux-and-safety into master

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: hippogrief/pobsync#14