Skip to content

armgit / Pulse

Public Imported from GitHub
0

Real-time monitoring dashboard for Proxmox VE, PBS, Docker, Kubernetes, TrueNAS and vSphere. Self-hosted, with alerts for failed backups, full disks, unhealthy containers and offline nodes.

Compose reviewed endpoint trust repair onto current main

pulse-triage[bot]b06ba4e50a61
diff --cc docs/release-control/v6/internal/subsystems/storage-recovery.md
index 5035da940b,c4e31f84b6..591827f49d
--- a/docs/release-control/v6/internal/subsystems/storage-recovery.md
+++ b/docs/release-control/v6/internal/subsystems/storage-recovery.md
@@@ -21,27 -21,22 +21,43 @@@
## Purpose
+### Restore-point origin is distinct from workload placement
+
+The existing frontend location scope retains the backup reader's connection
+as a display fact separately from its positional source/connection/repository
+key. Existing inventory and Coverage searches match the display connection,
+including an explicitly unknown origin, without changing exact filter keys.
+Existing inventory and Coverage consumers show that connection, including
+the full value in restore-point details and wrapped Coverage evidence. No guest
+node, namespace or workload connection supplies a missing backup origin.
+Same-named repositories remain independently identified; existing exact and
+legacy filter resolution, archive/PBS matching, native IDs, chronology, provider
+observations and protection policy are unchanged. No API shape, stored record,
+backup/restore or guest-agent operation changes.
+
+The normal-suite `backupSourceConnection.test.tsx` covers the real inventory
+producer and consumers for PBS, PVE archives and snapshots, unknown origins,
+same-point polling and literal rendering. `proxmoxBackupLocation.test.ts` keeps
+the exact key and compatibility controls. Desktop/narrow consuming browser
+proof establishes readable source selection, not original #3248/#2681 recovery
+or actual restore availability.
+
+ Disabled guest, storage and backup collection scopes remain disabled when a
+ trust edit is saved. Their false response values must survive the editor
+ round-trip rather than fall back to enabled new-connection defaults.
+ `TestPVEEndpointTrustEditorPreservesDisabledCollectors` verifies preservation.
+
+ ### Proxmox TLS recovery preserves storage and guest state
+
+ Reconciliation of saved API certificate trust is confined to the selected
+ endpoint authority/base path. It leaves backup/History data, guest identity,
+ credentials, discovered member records and unrelated pins intact. A saved
+ connection test reads the nodes API only and does not perform backup, restore,
+ freeze/thaw, filesystem, storage or guest-agent operations. Failure to persist
+ the PVE candidate does not publish its trust in memory.
+ `TestPVEEndpointTrustAdmission` and `TestPVEEndpointTrustSavedPolling` prove
+ these scoped save/probe boundaries, not installed backup or filesystem recovery.
+
### Backup retention never substitutes for verification
The existing restore-point State cell and drawer status prioritise running or