5 Commits

Include renames

Author	SHA1	Message	Date
Christian Manivong	75869eae06	chore: adopt the NAPALM driver standard ... - CI moves to .gitea/workflows/ci.yml and calls the shared driver workflow of NAPALM/driver-standard; .github/ is gone. - license = "Apache-2.0" and a LICENSE file: the package declared no license at all. README and CHANGELOG.md, py.typed, links to git.netork.io, a dev extra with floors; .venv/ and build output ignored. - Floors on every dependency: napalm-device-types>=4.21.1 (had none), napalm>=4.0 (what napalm-device-types needs) and requests>=2.28.0. Without them the lowest CI job resolves napalm 0.10, which does not build; the tests pass at exactly these floors. - mypy strict for the package; napalm_yealink.yealink is exempt for now (20 errors), recorded in the quality baseline with get_facts' complexity. Coverage floor 42 % (measured 42.61 %). Closes #4	2026-10-23 08:46:20 +02:00
Christian Manivong	4a4f9378c5	style: ruff format and the lint rules of the driver standard ... Mechanical: ruff format, and ruff check --fix with the rule set every NAPALM driver uses (E, F, I, UP, B at line length 100, Python 3.10). What ruff cannot fix comes in the next commit.	2026-10-23 08:42:02 +02:00
Christian Manivong	46ff971953	fix: drop stubs that claim what a phone cannot do (0.1.1) ... get_health_metrics, get_ssids, get_radio_info and get_wireless_clients only raised NotImplementedError. They are left over from when the driver sat on AccessPointDriver, and a stub makes a capability check (callable(getattr(driver, name))) answer yes. The application polls SNMP itself (napalm-device-types docs/STRUCTURE.md); a phone has no profile to declare. Also stops tracking the .pyc and egg-info files .gitignore already lists. Closes #2	2026-10-16 12:03:38 +02:00
Christian Manivong	33d07bed58	fix: inherit PhoneDriver, and stop asserting a contract the driver rejected ... Closes netork#117. A Yealink is a desk phone. It inherited AccessPointDriver because nothing better existed, and netOrk reads that role to populate its wireless page, its AP profile pickers and its SSID drift view — so a phone appeared in all three. napalm-device-types now has PhoneDriver. TYPE_LABEL comes from it, so the local override is gone. The two failing fingerprint tests were asserting the opposite of a deliberate decision. HTTP_FINGERPRINT carries "yealink" as a heavy but *not* mandatory rule, with the reason written next to it: some models answer / with a redirect to their API page, whose body says "yealink" nowhere, and a mandatory rule disqualifies the driver whenever its pattern is absent. Making it mandatory would rule out a real phone. The tests demanded it be mandatory, and the Cisco test then asserted `not all(...)` over an empty list, which is False. Both now check the property that actually protects against a false match: none of this driver's patterns appear on a Cisco page, so it contributes no score and never wins.	2026-08-21 13:07:37 +07:00
Christian ManivongandClaude Sonnet 4.6	60525bd35e	feat: initial napalm-yealink driver ... Discovery-Fingerprinting für Yealink IP-Phones (T-series, W-series, CP-series, VP-series) und Video-Endpoints. - TYPE_LABEL = "Phone" (Override von AccessPointDriver) - SNMP_OBJECT_ID_PREFIX = "1.3.6.1.4.1.37403" (Yealink Enterprise OID) - HTTP_FINGERPRINT: "yealink" (mandatory, weight 10), Modell-Patterns - get_facts(): liest phoneName + firmware aus dem noauth-API-Response (/api/v1/system/info liefert Gerätedaten auch ohne Authentication) - Login via MD5-gehashtem Passwort auf /api/v1/session/login (HTTPS) Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>	2026-06-24 15:17:08 +02:00