mirror of
https://github.com/rcourtman/Pulse.git
synced 2026-09-11 14:00:29 +00:00
rcourtman
f99bce7ee4
Pulse's primary monitored platform is Proxmox, but the per-command-class preflight catalog only covered systemd services, Docker containers, and Kubernetes deployments. Operators approving a Patrol-proposed qm restart/qm stop/qm shutdown saw the generic preflight without the operational nuance that distinguishes those verbs (qm stop is a hard halt, qm shutdown is graceful with a 60s ACPI timeout, etc.). Adds eight new classes covering qm and pct lifecycle (reboot/restart, stop, start, shutdown). Each gets hand-authored safety and verification copy that names the actual semantics — pct stop is destructive vs pct shutdown's lxc-attach handoff — so the operator sees concrete context at approval time. Broker-level VerificationCommandForCommand intentionally does not derive qm status / pct status from these classes — pulse_control's verifyGuestAction already runs those checks at the tool layer, so adding a parallel broker dispatch would double-run. The preflight copy still names what the tool-layer verification will read.