Skip to content

v0.6.0 — blast-radius coverage

Choose a tag to compare

@john-broadway john-broadway released this 19 Jun 15:26
· 31 commits to main since this release

0.6.0 — blast-radius coverage.

Ten blast-radius op-classes (#6–15) now read live cluster state at plan time and name the specific cross-resource consequences of dangerous operations — the guests a storage/disk change strands, the nodes a firewall change locks out of management, the ACL principals a pool/group/role/realm change orphans, the active disk a volume-delete destroys — so no destructive op falls back to a bare confirm.

  • pve_disk_move, pve_guest_migrate, the firewall lockout pair, pve_network_iface_update, pve_pool_delete / pve_group_delete / pve_role_update / pve_realm_update, pve_storage_content_delete, pve_backup_delete.
  • Each built test-first and adversarially redteamed; every pass caught (and fixed) a real under-flag.
  • No new tools (145); +86 tests (2308 → 2394), ruff + pyright clean. Backward-compatible.
  • Verified against a real Proxmox: PLAN-checks on live cluster data + a bounded allocate→delete→verify on an isolated test sandbox.

Published on PyPI (proximo-proxmox), GitHub, and GHCR (signed multi-arch). See CHANGELOG for full detail + the one logged deferred gap (PBS prune/namespace itemization).