Christian Manivong
2abf0a1a8f
driver / lint (pull_request) Successful in 15s
driver / standard (pull_request) Successful in 16s
driver / test (3.13) (pull_request) Successful in 1m1s
driver / types (pull_request) Successful in 1m6s
driver / test (3.12) (pull_request) Successful in 1m7s
driver / lowest (pull_request) Failing after 23s
driver / build (pull_request) Successful in 36s
driver / security (pull_request) Successful in 1m9s
CI / driver (pull_request) Failing after 2m30s
driver / publish (pull_request) Skipped
netOrk runs every driver in its own containers on Python 3.12, so 3.10 and 3.11 are no longer supported or tested. requires-python, mypy and ruff move to 3.12, along with what ruff's pyupgrade rules then rewrite.
1.8 KiB
1.8 KiB
Changelog
All notable changes to this driver. The format follows Keep a Changelog, versions follow Semantic Versioning.
[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).
[0.2.0] - 2026-10-23
The first release on PyPI.
Changed
- The driver follows the NAPALM driver standard
(https://git.netork.io/NAPALM/driver-standard): CI on Gitea runs ruff, 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. Python 3.10 stays the floor; the
license is declared as the SPDX string
Apache-2.0, next to the LICENSE file andpy.typedthe package already shipped. napalm-device-types now comes from PyPI (4.21.1 or later). - AMT's answers are parsed with defusedxml (a new dependency). An answer that carries a DTD is refused in any encoding; before, one in UTF-16 got through.
[0.1.1] - 2026-10-18
Fixed
SNMP_CAPABLE = False: AMT runs no SNMP agent, so netOrk does not poll it over SNMP as it does other management controllers.
[0.1.0] - 2026-10-18
Added
amtdriver (napalm_amt.AmtDriver), aManagementControllerDriverfor Intel AMT over WS-Management: facts, AMT's network port, hardware inventory with the SMBIOS system UUID, firmware (AMT with build, BIOS), power state and power control, the hardware event log, and what AMT listens on (plain HTTP or TLS, KVM, virtual media).- Discovery: ports 16992/16993 and AMT's name in the
Serverheader and web UI. python -m napalm_amt.record: records a real AMT's answers as fixtures, read-only.