napalm-bsd has no apply_updates. The application carries the BSD upgrade commands itself (NetOrk/netork netork/jobs/tasks/updates/apply.py ~79–104: pkg_add -u -I, running syspatch twice, freebsd-update … install, the FreeBSD-base repository check). That is device code in the wrong layer. UpdateMixin already declares apply_updates.
Change: implement apply_updates here with those commands and tests; the application then calls the driver.
Part of NetOrk/netork#1105. Plan: NAPALM/napalm-device-types docs/STRUCTURE.md (branch docs/structure-plan).
Prio P3.
napalm-bsd has no `apply_updates`. The application carries the BSD upgrade commands itself (NetOrk/netork `netork/jobs/tasks/updates/apply.py` ~79–104: `pkg_add -u -I`, running `syspatch` twice, `freebsd-update … install`, the `FreeBSD-base` repository check). That is device code in the wrong layer. `UpdateMixin` already declares `apply_updates`.
Change: implement `apply_updates` here with those commands and tests; the application then calls the driver.
Part of NetOrk/netork#1105. Plan: NAPALM/napalm-device-types `docs/STRUCTURE.md` (branch `docs/structure-plan`).
Prio P3.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
napalm-bsd has no
apply_updates. The application carries the BSD upgrade commands itself (NetOrk/netorknetork/jobs/tasks/updates/apply.py~79–104:pkg_add -u -I, runningsyspatchtwice,freebsd-update … install, theFreeBSD-baserepository check). That is device code in the wrong layer.UpdateMixinalready declaresapply_updates.Change: implement
apply_updateshere with those commands and tests; the application then calls the driver.Part of NetOrk/netork#1105. Plan: NAPALM/napalm-device-types
docs/STRUCTURE.md(branchdocs/structure-plan).Prio P3.