Remove the napalm_driver and napalm_args fields from Platform #7933

Closed
opened 2025-12-29 20:30:12 +01:00 by adam · 1 comment
Owner

Originally created by @jeremystretch on GitHub (Apr 21, 2023).

Originally assigned to: @jeremystretch on GitHub.

Proposed Changes

Remove the napalm_driver and napalm_args fields from the Platform model.

Justification

NAPALM integration was moved to a plugin in NetBox v3.5 under #10520. These fields were retained to ease migration to the plugin, but are no longer needed once the plugin has been installed.

Originally created by @jeremystretch on GitHub (Apr 21, 2023). Originally assigned to: @jeremystretch on GitHub. ### Proposed Changes Remove the `napalm_driver` and `napalm_args` fields from the Platform model. ### Justification NAPALM integration was moved to a [plugin](https://github.com/netbox-community/netbox-napalm) in NetBox v3.5 under #10520. These fields were retained to ease migration to the plugin, but are no longer needed once the plugin has been installed.
adam added the status: acceptedtype: deprecation labels 2025-12-29 20:30:12 +01:00
adam closed this issue 2025-12-29 20:30:13 +01:00
Author
Owner

@PieterL75 commented on GitHub (Jun 22, 2023):

@jeremystretch Can we keep the 'driver' field ?
My automation uses napalm, and gets the driver from the Platform assigned to the Device.
Maybe just rename it to 'DeviceDriver' in stead of NapalmDriver ?
Other option is to use CustomFields, but it feels like a proper field to retain on the Platform model

@PieterL75 commented on GitHub (Jun 22, 2023): @jeremystretch Can we keep the 'driver' field ? My automation uses napalm, and gets the driver from the Platform assigned to the Device. Maybe just rename it to 'DeviceDriver' in stead of NapalmDriver ? Other option is to use CustomFields, but it feels like a proper field to retain on the Platform model
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#7933