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

Add YAML Input for Config Contexts #6030

New Issue
Closed
opened 2025-12-29 19:35:52 +01:00 by adam · 2 comments
adam commented 2025-12-29 19:35:52 +01:00
Owner
Copy Link

Originally created by @romulus-ai on GitHub (Feb 1, 2022).

NetBox version

v3.1.6

Feature type

Change to existing functionality

Proposed functionality

Configcontexts currently could only be added in JSON Format, however they could be displayed as YAML as well. Since YAML is the more comfortable format to add configuration Data it would be nice to be able to add config contexts in YAML format.

I.e. you could allow to add YAML configuration and translate it to JSON before you save it in the DB, this way only a change of the View and/or Controller should be neccessary.

Use case

It is much easier to manually manipulate YAML Text instead of JSON, additionally an example.

When you use Netbox as Inventory source for you ansible Playbooks, the transfer of the inventory configuration written in YAML would be much much easier than translating this YAML to JSON first manually.

Database changes

Don't think that there are any DB Changes neccessary

External dependencies

Don't think there are external Dependencies neccessary

Originally created by @romulus-ai on GitHub (Feb 1, 2022). ### NetBox version v3.1.6 ### Feature type Change to existing functionality ### Proposed functionality Configcontexts currently could only be added in JSON Format, however they could be displayed as YAML as well. Since YAML is the more comfortable format to add configuration Data it would be nice to be able to add config contexts in YAML format. I.e. you could allow to add YAML configuration and translate it to JSON before you save it in the DB, this way only a change of the View and/or Controller should be neccessary. ### Use case It is much easier to manually manipulate YAML Text instead of JSON, additionally an example. When you use Netbox as Inventory source for you ansible Playbooks, the transfer of the inventory configuration written in YAML would be much much easier than translating this YAML to JSON first manually. ### Database changes Don't think that there are any DB Changes neccessary ### External dependencies Don't think there are external Dependencies neccessary
adam added the type: featurestatus: needs ownerpending closure labels 2025-12-29 19:35:52 +01:00
adam closed this issue 2025-12-29 19:35:52 +01:00
adam commented 2025-12-29 19:35:53 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (May 30, 2022):

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.

@github-actions[bot] commented on GitHub (May 30, 2022): 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](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
adam commented 2025-12-29 19:35:53 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jun 29, 2022):

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 (Jun 29, 2022): 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 status: needs owner 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#6030
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?