Closes#50. netOrk side: NetOrk/netork#1888 (the capability appears with the napalm-proxmox pin bump of the 0.47.0 sweep, no netOrk code).
run_command(command, *, privileged=False, timeout=60, stdin=None) -> CommandResult on an exec channel of _node_ssh() via napalm_device_types.channel.run_on_transport. privileged needs nothing more because the node is logged in as root. Errors and timeouts raise ConnectionException, as _exec_ssh_command does.
OpenSshServerMixin in the bases: harden_ssh_server, exempt_from_ssh_penalties.
USES_SSH comment corrected; the flag itself is unchanged (netOrk reads it as "netOrk does not log in over SSH itself").
Tested: 6 new tests (red before, green after), full suite 512 passed, ruff, format, mypy, napalm-standard check + ratchet, bandit. Read-only live check on a PVE 9.2 cluster node: run_command returned stdout, stderr and exit code separately as root, and get_ssh_server_algorithms() read sshd -T through it. Nothing was changed on the host.
Closes #50. netOrk side: NetOrk/netork#1888 (the capability appears with the napalm-proxmox pin bump of the 0.47.0 sweep, no netOrk code).
- `run_command(command, *, privileged=False, timeout=60, stdin=None) -> CommandResult` on an exec channel of `_node_ssh()` via `napalm_device_types.channel.run_on_transport`. `privileged` needs nothing more because the node is logged in as root. Errors and timeouts raise `ConnectionException`, as `_exec_ssh_command` does.
- `OpenSshServerMixin` in the bases: `harden_ssh_server`, `exempt_from_ssh_penalties`.
- `USES_SSH` comment corrected; the flag itself is unchanged (netOrk reads it as "netOrk does not log in over SSH itself").
Tested: 6 new tests (red before, green after), full suite 512 passed, ruff, format, mypy, `napalm-standard check` + `ratchet`, bandit. Read-only live check on a PVE 9.2 cluster node: `run_command` returned stdout, stderr and exit code separately as root, and `get_ssh_server_algorithms()` read `sshd -T` through it. Nothing was changed on the host.
A Proxmox node runs Debian's stock OpenSSH, so OpenSshServerMixin works
there as on a plain Linux host. What it needed was run_command: an exec
channel on the node's SSH session, via napalm-device-types'
run_on_transport. The USES_SSH comment said there was no SSH session;
it now says what the flag means to netOrk.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Closes #50. netOrk side: NetOrk/netork#1888 (the capability appears with the napalm-proxmox pin bump of the 0.47.0 sweep, no netOrk code).
run_command(command, *, privileged=False, timeout=60, stdin=None) -> CommandResulton an exec channel of_node_ssh()vianapalm_device_types.channel.run_on_transport.privilegedneeds nothing more because the node is logged in as root. Errors and timeouts raiseConnectionException, as_exec_ssh_commanddoes.OpenSshServerMixinin the bases:harden_ssh_server,exempt_from_ssh_penalties.USES_SSHcomment corrected; the flag itself is unchanged (netOrk reads it as "netOrk does not log in over SSH itself").Tested: 6 new tests (red before, green after), full suite 512 passed, ruff, format, mypy,
napalm-standard check+ratchet, bandit. Read-only live check on a PVE 9.2 cluster node:run_commandreturned stdout, stderr and exit code separately as root, andget_ssh_server_algorithms()readsshd -Tthrough it. Nothing was changed on the host.