mirror of
https://github.com/rcourtman/Pulse.git
synced 2026-10-26 13:39:47 +00:00
rcourtman
43efbb9152
The only way to give an agent the command access that Docker and Podman container updates need was a checkbox called "Enable legacy combined command profile", behind "Show advanced connection and install options", which only appeared after the install token was minted. The name told the users who want updates not to use it, and #1728 shows a user missing it entirely and hand-editing token scopes instead. It is not being retired for container updates yet. Updates dispatch through the agent command session; the separate action runner's container actions are unqualified, and rootful Docker under the safe collector profile has no update checks or actions. So the option stays, with the same security posture: off by default, an explicit choice mints an execution-scoped token and records command-capable, and a monitoring-only install still cannot be promoted remotely. The checkbox now reads "Allow Pulse to run commands on this host" and sits in the token step, so the choice is made before the credential is minted. Its description says what it enables, that Pulse can then run commands as root, and that it cannot be switched on later from Pulse. The token summary no longer claims commands can be enabled per host from Settings. One shared label feeds the installer, the locked Docker update pill and the Proxmox setup guide, and the docs name the option the same way.