napalm-bsd

4 Commits

Author	SHA1	Message	Date
Christian Manivong	d06da7cc8b	feat!: configure_snmp_agent with the caller's values replaces fix_snmp (0.3.0) CI / test (3.10) (push) Successful in 34s Details CI / test (3.11) (push) Successful in 30s Details CI / test (3.12) (push) Successful in 34s Details fix_snmp wrote an application's snmpd.conf (community public, Managed by netOrk, netork@localhost) and judged itself by a local snmpget. The drivers implement napalm-device-types 4.13's SnmpAgentMixin steps instead: net-snmp installed, snmpd.conf with one rocommunity line per allowed source (staged without privilege, installed by root), snmpd enabled and restarted. pf and ipfw rules stay the operator's. A community or text that would break the file is refused. The caller verifies with its own SNMP client. Also get_management_peer() from SSH_CONNECTION, ensure_package from the base package, and get_snmp_config no longer assumes "public". BREAKING CHANGE: run_device_action is removed. Requires napalm-device-types 4.13. Closes #12	2026-10-17 00:53:00 +02:00
Christian Manivong	707e048792	fix: keep the sudo password out of files written as root (0.2.1) CI / test (3.10) (push) Successful in 27s Details CI / test (3.11) (push) Successful in 27s Details CI / test (3.12) (push) Successful in 25s Details CI / test (3.10) (pull_request) Successful in 29s Details CI / test (3.11) (pull_request) Successful in 24s Details CI / test (3.12) (pull_request) Successful in 25s Details run_command prepended the sudo password to the caller's stdin. A sudo that does not prompt left it for the command, and fix_snmp's 'cat > snmpd.conf' wrote it as the configuration's first line before making the file world-readable. run_command now refuses stdin to a privileged command while a sudo password is set. fix_snmp stages the configuration in a mktemp file without privilege, and root installs it next to the target and renames it over, so nothing root runs follows a symlink. Closes #8	2026-10-16 11:48:25 +02:00
Christian Manivong	32a63411d3	feat: say whether a host is still in its first boot CI / test (3.10) (push) Successful in 29s Details CI / test (3.11) (push) Successful in 30s Details CI / test (3.12) (push) Successful in 29s Details CI / test (3.10) (pull_request) Successful in 29s Details CI / test (3.11) (pull_request) Successful in 46s Details CI / test (3.12) (pull_request) Successful in 42s Details first_boot_pending() is true while /firstboot exists on FreeBSD. A FreeBSD cloud image upgrades its base system on its first boot, starts sshd only after that and restarts right away, and /etc/rc removes /firstboot just before that restart. netOrk waits for this before it sets up a new VM (NetOrk/netork#795). OpenBSD has no such marker to ask yet, so it returns False there.	2026-10-08 12:58:00 +02:00
Christian Manivong	25308bf747	fix: raise when an update reader cannot read, and report host status CI / test (3.10) (push) Successful in 26s Details CI / test (3.11) (push) Successful in 25s Details CI / test (3.12) (push) Successful in 26s Details CI / test (3.10) (pull_request) Successful in 25s Details CI / test (3.11) (pull_request) Successful in 24s Details CI / test (3.12) (pull_request) Successful in 26s Details netOrk reads an empty update list as "no updates" and closes every patch clock on the host. A refused sudo, a failing pkg, syspatch or freebsd-update, or a pkg database pkg cannot read used to come back as that empty list. Each of these now raises. Only pkg's "is not installed" still means no packages. BsdDriver takes on napalm-device-types' HostStatusMixin. On FreeBSD it reports a host whose installed kernel differs from the running one as needing a reboot (device-types 4.1). OpenBSD stays unknown. Closes #4	2026-10-08 12:08:44 +02:00