Repository navigation
v0.49.1: shell calls across a cluster, and the operator's wait
Shell calls across a cluster, and the operator's wait. A patch: one new registry table and one new variable, both off until set; nothing an existing setup sends changes.
Route PVE shell rows by target and node. From RavenLiao, PR #107 (the node-routing half of #98). A named PVE target may map the node names in a path to OpenSSH destinations under [targets.<name>.nodes]. The five shell rows use that map for plans, execution and diagnosis. A missing mapping refuses before consent, rate slots, the safety snapshot or any read, and a named target never falls back to PROXIMO_SSH_TARGET. The far end must still answer as the path's node before pct runs. The default box is unchanged.
The shell wait is the operator's. PROXIMO_SHELL_TIMEOUT sets how long one shell call waits for its command, in whole seconds from 1 to 600; unset is the 60 it always was. Any other value refuses every shell call before anything dials, and proximo doctor reports the effective wait or flags it. No argument a model sends moves it. Issue #106.
Also: CI actions bumped, each pinned by the SHA of its release (#105), and a shell path's container id is ASCII digits only.
4,186 tests.
Full history for this release, commit by commit, is on the internal mirror; this public branch carries one squashed commit per release by design. Every change here is described in CHANGELOG.md.
Where to read more
- Shell lanes, node routing and the wait: docs/SETUP.md
- What each control honestly holds: SECURITY.md
- Verifying the image signature, the SBOM and the provenance yourself: VERIFY.md
- Full change detail: CHANGELOG.md
Install: uvx proximo-proxmox · pip install proximo-proxmox · ghcr.io/john-broadway/proximo:0.49.1