driver / lint (pull_request) Successful in 17s
driver / standard (pull_request) Failing after 18s
driver / types (pull_request) Successful in 1m7s
driver / test (3.13) (pull_request) Successful in 1m3s
driver / test (3.12) (pull_request) Successful in 1m7s
driver / lowest (pull_request) Successful in 33s
driver / build (pull_request) Successful in 28s
driver / security (pull_request) Successful in 1m1s
CI / driver (pull_request) Failing after 2m22s
driver / publish (pull_request) Skipped
apt's https method asks Acquire::https::Proxy and then Acquire::http::Proxy, for the host and then for all. An 00proxy with the http line alone therefore sent download.docker.com and every other https source to apt-cacher-ng, which answers 403 CONNECT denied without a PassThroughPattern, and the whole upgrade failed. - The report carries https_proxy, https_per_host and https_settings; https_proxy_for(report, host) is the proxy apt takes for one https host. - check_https_source() fetches one https source the way apt does. - configure_package_proxy gains an https step: one https source through the new proxy. Where the proxy refuses it, 00proxy also says Acquire::https::Proxy "DIRECT", later https lines to the same proxy are commented out, and the source is fetched direct. An HTTP error from the mirror counts as let through. - apt_fetch_command takes https URLs; comment_out_command takes a scheme.
7.2 KiB
7.2 KiB
Changelog
All notable changes to napalm-device-types. The format follows Keep a Changelog, versions follow Semantic Versioning. Versions up to 4.21.0 were not recorded here; their history is the git log.
[Unreleased]
Changed
- Python 3.12 is the floor (
requires-python = ">=3.12"): netOrk runs every driver on 3.12, so 3.10 and 3.11 are no longer tested (NAPALM/driver-standard#6). - The floor on napalm is 5.1: older releases import
pkg_resources, which a Python 3.12 venv no longer has.
Added
LocalAccountsMixin(napalm_device_types.local_accounts): personal login accounts on a host.get_local_accounts(names)reads them back (groups, lock, sudo, key files),add_local_account(name, public_key, password_hash=, admin=)creates or reopens one,lock_local_account(name)takes its keys and sudo away and refuses every login while keeping its home. Every command root runs is one fixed command, the key files are read and written as the account itself, and the sudo rule is a drop-in of its own, checked withvisudoandsudo -l. A driver supplies the commands that create, open and lock an account and take it out of a group, and may replace where the keys are kept (_account_key_files,_account_read_keys,_account_add_key,_account_remove_keys; default~/.ssh/authorized_keys) (NetOrk/netork#1793).OpenSshServerMixin.exempt_from_ssh_penalties: puts the address the host sees the managing client at ($SSH_CONNECTION) intoPerSourcePenaltyExemptList, in/etc/ssh/sshd_config.d/00-netork-penalty-exempt.conf, next to the host's own exemptions. Only where sshd has per-source penalties (OpenSSH 9.8+; an older one refuses the directive) and sshd_config includes the drop-in directory; checked withsshd -tandsshd -T, then a new session, and taken back on any failure. Helpers:parse_penalty_exemptions,client_address,is_exempt(NetOrk/netork#1800).retry_refusedandrefused_before_banner(napalm_device_types.ssh_host_keys): a connection sshd closes before its banner -- what OpenSSH 9.8+ does to a source it has just penalised -- is tried again after 1, 3, 7 and 15 s.HostKeyCheck.connectdoes so itself (NetOrk/netork#1800).ARP_AGE_UNKNOWN(napalm_device_types.arp,-1.0): theagea driver reports inget_arp_tableandget_ipv6_neighbors_tablewhen the device does not say how old an entry is.0.0means "confirmed just now" and is no stand-in for it (NetOrk/netork#1327).NetworkTargetDict.uplinks(optional): the physical NICs a bridge leaves the host through, one group per way out -- a bond's slaves together, a single NIC alone ([["eno1", "eno2"]]). A missing key means unknown, an empty list a bridge without uplink. NetOrk follows their LLDP neighbours to the switch port and its untagged VLAN; one slave's neighbour speaks for its bond (NetOrk/netork#1325).HostShutdownMixin.shutdown_host(), onDeviceTypeDriver: shut the device itself down cleanly through its own means; declared, sohasattrsays whether a driver can. No forced variant (NetOrk/netork#1636).VmStopRequestMixin.begin_stop_vm(name): ask for a VM's clean shutdown and return at once, for callers that wait on a timer instead of instop_vm. No role demands it (NetOrk/netork#1636).SudoHistoryMixin(napalm_device_types.sudo_history): the sudo password an earlier driver typed into an interactive shell (echo '<password>' | sudo -S -p "" …) and left in the login user's shell history, for a driver to mix in (NetOrk/netork#1090). The driver says what its lines carry (SUDO_HISTORY_MARKER) and which files its partial sudo left to the login user (SUDO_ROOT_FILES), and suppliesrun_command.get_history_sudo_lines()counts the lines per history file (~/.bash_history,~/.zsh_history,~/.ash_history,~/.sh_history) withgrep -cas the login user. No line is read back; a file it cannot read raises.remove_history_sudo_lines()deletes exactly those lines as the login user (sed -i, its backup overwritten withshred -u), and as root gives each ofSUDO_ROOT_FILESback toroot:rootwhere it is a regular file, not a symbolic link, owned by the login user. It reports every file's lines before and after, how many were removed and which files are root's again. Nothing goes to stdin.
Fixed
AptProxyMixinknows that apt's https sources take the http proxy too: apt's https method asksAcquire::https::Proxyand thenAcquire::http::Proxy, for the host and then for all. An00proxywith the http line alone sent download.docker.com and every other https source to apt-cacher-ng, which answers403 CONNECT deniedwithout aPassThroughPattern, and the whole upgrade failed (NetOrk/netork#1811).- The report carries
https_proxy,https_per_hostandhttps_settings;https_proxy_for(report, host)is the proxy apt takes for one https host. check_https_source()fetches one https source'sInReleasethe way apt does; None where no https source goes through a proxy.configure_package_proxygains anhttpsstep: one https source through the new proxy. Where the proxy refuses it,00proxyalso saysAcquire::https::Proxy "DIRECT";, later https lines to the same proxy are commented out, and the source is fetched direct. An HTTP error from the mirror counts as let through.apt_fetch_commandtakes https URLs;directsets the host's https setting too.comment_out_command(..., scheme="https").
- The report carries
[4.22.0] - 2026-10-23
Added
AptProxyMixin(napalm_device_types.apt_proxy): apt's proxy on a Debian-family host, for a driver to mix in (NetOrk/netork#1397).get_package_proxy()is the proxy apt really fetches through, asapt-config dumpsays, and no longer the content of one file. A proxy the Debian or Ubuntu installer set elsewhere wins over00proxy, and was missed.get_package_proxy_report()adds where it is set: every line of apt's configuration that sets it, in the order apt reads them, the per-host proxies, and the sources fetched over http and over https.check_package_proxy(url, expect)fetches a page from the host with apt's own downloader, past any proxy, and says whether the host reached it and whether the page says what you expected.configure_package_proxy(url)writes the proxy, comments out every other line that sets a different one, reads the result back and fetches one source through the proxy. It fails when apt still fetches elsewhere.same_proxy_url()compares two proxy URLs by scheme, host and port.
[4.21.1] - 2026-10-22
The first release on PyPI since 0.1.0.
Changed
- The package follows the NAPALM driver standard (https://git.netork.io/NAPALM/driver-standard): CI on Gitea runs ruff, strict mypy, the tests on Python 3.10–3.13 and at the lowest declared versions, bandit, pip-audit and a build check, and a release tag publishes to PyPI.
- Type annotations use builtin generics (
list[str],X | None) instead oftyping.ListandOptional. They mean the same to a type checker. - The project links point at git.netork.io instead of GitHub.