-
Notifications
You must be signed in to change notification settings - Fork 2.7k
Use HTMX to render device status/config/LLDP views #8152
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Labels
needs milestone
Awaiting prioritization for inclusion with a future NetBox release
type: feature
Introduction of new functionality to the application
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Please see our contributing guide. |
Closing this out, to be revisited once NetBox's NAPALM proxy functionality has been moved to a plugin per #10520. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
needs milestone
Awaiting prioritization for inclusion with a future NetBox release
type: feature
Introduction of new functionality to the application
Proposed Changes
There are three subviews available under the device view which employ NAPALM to poll a live device:
These views leverage the
/napalm/
endpoint under the REST API endpoint for devices to fetch this live data. Javascript handles the application of the received data to the DOM for presentation to the user.This issue proposes two major changes:
Justification
Processing the returned NAPALM data within the UI view affords us considerably more flexibility over what to do with the data, and greatly simplifies client side requirements. By moving this logic under the UI view, we obviate the need for the three standalone Javascript modules (
status.js
,lldp.js
, andconfig.js
) that exist today.Additionally, relocating the NAPALM connection logic outside of the REST API view should make for cleaner code, however that isn't dependent on this overall change.
The text was updated successfully, but these errors were encountered: