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

Representation of data in YANG format #7431

New Issue
Closed
opened 2025-12-29 20:23:24 +01:00 by adam · 4 comments
adam commented 2025-12-29 20:23:24 +01:00
Owner
Copy Link

Originally created by @misch42 on GitHub (Dec 29, 2022).

NetBox version

v.3.3

Feature type

New functionality

Proposed functionality

Hi,

I asked this feature in issue #4318 for a data representation in YANG format.

From my question on the community day I open this issue again.

Use case

Modern devices can be configured with data in YANG representation direct. So it would be cool to have a API entry point to gather the device data direct in YANG format. Configuration of devices or elements of devices could be applied directly without the need of re-formatting the data in ansible or saltstack.

This will make the configuration of devices out of netbox much easier.

Database changes

none.

External dependencies

none

Originally created by @misch42 on GitHub (Dec 29, 2022). ### NetBox version v.3.3 ### Feature type New functionality ### Proposed functionality Hi, I asked this feature in issue #4318 for a data representation in YANG format. From my question on the community day I open this issue again. ### Use case Modern devices can be configured with data in YANG representation direct. So it would be cool to have a API entry point to gather the device data direct in YANG format. Configuration of devices or elements of devices could be applied directly without the need of re-formatting the data in ansible or saltstack. This will make the configuration of devices out of netbox much easier. ### Database changes none. ### External dependencies none
adam added the type: featurepending closure labels 2025-12-29 20:23:24 +01:00
adam closed this issue 2025-12-29 20:23:25 +01:00
adam commented 2025-12-29 20:23:25 +01:00
Author
Owner
Copy Link

@jsenecal commented on GitHub (Jan 3, 2023):

Hi @misch42, did you have any implementation details in mind for this? As mentioned in the previous issue this is quite the undertaking.

@jsenecal commented on GitHub (Jan 3, 2023): Hi @misch42, did you have any implementation details in mind for this? As mentioned in the previous [issue](https://github.com/netbox-community/netbox/issues/4318#issuecomment-598508587) this is quite the undertaking.
adam commented 2025-12-29 20:23:26 +01:00
Author
Owner
Copy Link

@misch42 commented on GitHub (Jan 3, 2023):

I can imagine that this is a quite big task. On the other hand the reward would be quite interesting. I thought about a secondary API entry point that shows all the data in YANG format. Like https://netbox/api/yang/interfaces/42/.

A config management system could use these data direct and push this config via netconf to the device.

At the moment ansible or saltstack has to re-format the data from the netbox api into a format the the device understands.

An additional advantage would be that the config data of devices in YANG format in an ideal world would NOT be manufacturer dependent any more. A management system could push the config for the same device today to a device of manufacturer A and tomorrow to a device of manufacturer B.

Michael.

@misch42 commented on GitHub (Jan 3, 2023): I can imagine that this is a quite big task. On the other hand the reward would be quite interesting. I thought about a secondary API entry point that shows all the data in YANG format. Like https://netbox/api/yang/interfaces/42/. A config management system could use these data direct and push this config via netconf to the device. At the moment ansible or saltstack has to re-format the data from the netbox api into a format the the device understands. An additional advantage would be that the config data of devices in YANG format in an ideal world would NOT be manufacturer dependent any more. A management system could push the config for the same device today to a device of manufacturer A and tomorrow to a device of manufacturer B. Michael.
adam commented 2025-12-29 20:23:26 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Apr 4, 2023):

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. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Apr 4, 2023): 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. **Do not** attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
adam commented 2025-12-29 20:23:26 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (May 5, 2023):

This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.

@github-actions[bot] commented on GitHub (May 5, 2023): This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.
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 pending closure type: feature
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#7431
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?