NAPALM/napalm-windows
1
0 Fork 0
Code Issues 1 Pull Requests Actions Packages Projects Releases Wiki Activity
10 Commits 1 Branch 1 Tag
211ed27c9eb908dc728e41ee7b16bc08cb424b9a
Commit Graph
3 Commits
Author SHA1 Message Date
Christian Manivong d43d697700 chore: adopt the NAPALM driver standard
driver / standard (pull_request) Successful in 15s
Details
driver / lint (pull_request) Successful in 11s
Details
driver / types (pull_request) Successful in 44s
Details
driver / test (3.10) (pull_request) Successful in 46s
Details
driver / test (3.11) (pull_request) Successful in 45s
Details
driver / test (3.12) (pull_request) Successful in 42s
Details
driver / test (3.13) (pull_request) Successful in 38s
Details
driver / lowest (pull_request) Successful in 22s
Details
driver / security (pull_request) Successful in 45s
Details
driver / build (pull_request) Successful in 22s
Details
CI / driver (pull_request) Successful in 5m30s
Details
driver / publish (pull_request) Skipped
Details 
- CI moves to .gitea/workflows/ci.yml and calls the shared driver workflow
  of NAPALM/driver-standard; .github/ is gone.
- requires-python >=3.10 (napalm-device-types needs it), LICENSE file,
  py.typed, setuptools>=77 with the SPDX license string, Issues and
  Changelog links on git.netork.io, napalm-device-types>=4.21.1 from PyPI,
  floors on the dev extra.
- mypy strict for the whole package, no module exempt: optional_args is
  dict[str, Any] | None.
- tests/quality_baseline.json records get_facts and get_route_to, over
  complexity 10. Coverage floor 95 % (measured 95.67 %).
- CHANGELOG.md in Keep a Changelog form; the README says no host output is
  recorded yet, links napalm-device-types in the NAPALM org and pypsrp on
  PyPI.
 2026-10-23 08:49:27 +02:00
Christian Manivong a6814ad92e feat: report what listens, and which Windows service it is 
One script: Get-NetTCPConnection -State Listen, Get-NetUDPEndpoint, the
processes holding them and Win32_Service's PIDs. A process running one
service names it; a shared svchost runs several, and which of them holds
the socket Windows does not say, so it names none. http.sys sockets
(WinRM, IIS, SMB) belong to the System process.

The fixture is synthetic: no Windows host was at hand. tools/harvest.py
records the real output. For netOrk#673.
 2026-10-07 07:20:27 +02:00
Christian Manivong 1ce42ef099 feat: NAPALM driver for Windows over PowerShell Remoting 
Talks PSRP over WinRM via pypsrp, one runspace pool per connection. Each
getter sends one PowerShell script that projects cmdlet results onto flat
fields and ends in ConvertTo-Json, so the Python side parses JSON, not text.

Covers facts, interfaces, IP addresses, ARP, routes and services, plus
service start/stop/restart/enable/disable. Service names are validated and
quoted as PowerShell verbatim strings, typographic quotes included.

Fixtures are synthetic: they pin down the JSON the scripts are designed to
emit. tools/harvest.py records the real output from a host.

Refs christianmanivong/netork#300
 2026-09-24 09:23:25 +02:00