Duckboot/cv4pve-cli-tui
1
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Flag guests that no backup job covers #9

New Issue
Closed
opened 2026-11-02 22:55:41 +01:00 by Duckboot · 0 comments
Duckboot commented 2026-11-02 22:55:41 +01:00
Owner
Copy link
Copy source

Why

A guest that no backup job covers is the most likely way to lose data, and nothing in the TUI points it out today. The info screen only shows "No backup job covers this guest" when you open that guest.

Proposal

  • The main screen marks unprotected guests, for example a ! or a "Backup" column with no job.
  • The frame subtitle shows a count, for example "2 guests without backup job".
  • Optional: show the age of the newest backup and flag it as stale when it is older than N days.

cv4pve-cli (2.4.0)

  • get cluster not-backed-up. The format still needs checking.
  • Alternative: cli.backup_jobs() and cli.covering_jobs() already exist and give the same answer without extra calls.

Done when

  • Guests without a covering job are marked in the main table.
  • Tests are written first.
  • A read-only live check against mainframe passes.

Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com

## Why A guest that no backup job covers is the most likely way to lose data, and nothing in the TUI points it out today. The info screen only shows "No backup job covers this guest" when you open that guest. ## Proposal - The main screen marks unprotected guests, for example a `!` or a "Backup" column with `no job`. - The frame subtitle shows a count, for example "2 guests without backup job". - Optional: show the age of the newest backup and flag it as stale when it is older than N days. ## cv4pve-cli (2.4.0) - `get cluster not-backed-up`. The format still needs checking. - Alternative: `cli.backup_jobs()` and `cli.covering_jobs()` already exist and give the same answer without extra calls. ## Done when - Guests without a covering job are marked in the main table. - Tests are written first. - A read-only live check against mainframe passes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Duckboot added the
priority
1-high
 label 2026-11-02 22:55:41 +01:00
Sign in to join this conversation.
No Branch/Tag Specified
Labels
Clear labels
priority
1-high
Do first: biggest safety or maintenance gain
priority
2-medium
Next: clear everyday value
priority
3-low
Useful, but less often needed
priority
4-nice-to-have
Small conveniences; do when convenient
No labels
priority
1-high
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
Duckboot (Per-Arne Hellarvik)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Duckboot/cv4pve-cli-tui#9