starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Data representation in yang format #3441

New Issue
Closed
opened 2025-12-29 18:29:09 +01:00 by adam · 1 comment
adam commented 2025-12-29 18:29:09 +01:00
Owner
Copy Link

Originally created by @misch42 on GitHub (Mar 5, 2020).

Environment

  • Python version: 3
  • NetBox version: 2.7.3

Proposed Functionality

It would be rather cool to have data representation in the API in a format given by the YANG modeling. i.e. the interfaces would follow the RFC 8343 model.

With that data representation the data from netbox could directly used to configure the lasted deivce models of the big vendors.

Use Case

USe data from netbox directly to configure devices independent from the vendor.

At the moment we have to use ansbile or saltstack to configure devices according to their vendor. Also an ansible playbook configuring switch interfaces is quite large.

So, besides the normal data repesentation in the API, you could perhaps add a switch like (?format=<yang|netbox> to choose which form to output.

Database Changes

No.

External Dependencies

No.

Originally created by @misch42 on GitHub (Mar 5, 2020). ### Environment * Python version: 3 * NetBox version: 2.7.3 ### Proposed Functionality It would be rather cool to have data representation in the API in a format given by the YANG modeling. i.e. the interfaces would follow the RFC 8343 model. With that data representation the data from netbox could directly used to configure the lasted deivce models of the big vendors. ### Use Case USe data from netbox directly to configure devices independent from the vendor. At the moment we have to use ansbile or saltstack to configure devices according to their vendor. Also an ansible playbook configuring switch interfaces is quite large. So, besides the normal data repesentation in the API, you could perhaps add a switch like (?format=<yang|netbox> to choose which form to output. ### Database Changes No. ### External Dependencies No.
adam closed this issue 2025-12-29 18:29:09 +01:00
adam commented 2025-12-29 18:29:10 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Mar 13, 2020):

Sorry, this is way too big an undertaking to consider at this time. Maybe we can revisit it in the future.

@jeremystretch commented on GitHub (Mar 13, 2020): Sorry, this is way too big an undertaking to consider at this time. Maybe we can revisit it in the future.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#3441
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?