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 support for YAML format in JSON text areas #9121

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

Originally created by @balporig on GitHub (Jan 21, 2024).

NetBox version

v3.7.1

Feature type

Change to existing functionality

Proposed functionality

Add support for entering YAML instead of JSON in all text input areas that currently accept only JSON such as Config Contexts. The field previews already have the option to view between JSON/YAML

Use case

YAML is more human-readable and less verbose. Useful in cases you have the data already in YAML format for eg. coming from Ansible group vars, and you don't want to deal with JSON conversion

Database changes

No response

External dependencies

No response

Originally created by @balporig on GitHub (Jan 21, 2024). ### NetBox version v3.7.1 ### Feature type Change to existing functionality ### Proposed functionality Add support for entering YAML instead of JSON in all text input areas that currently accept only JSON such as Config Contexts. The field previews already have the option to view between JSON/YAML ### Use case YAML is more human-readable and less verbose. Useful in cases you have the data already in YAML format for eg. coming from Ansible group vars, and you don't want to deal with JSON conversion ### Database changes _No response_ ### External dependencies _No response_
adam added the type: featurestatus: needs ownerpending closurecomplexity: medium labels 2025-12-29 20:45:54 +01:00
adam closed this issue 2025-12-29 20:45:55 +01:00
adam commented 2025-12-29 20:45:55 +01:00
Author
Owner
Copy Link

@jeffgdotorg commented on GitHub (Apr 3, 2024):

Thanks for your interest in helping make NetBox better. I'm moving this issue along to needs owner so that a developer with spare capacity can pick it up.

@jeffgdotorg commented on GitHub (Apr 3, 2024): Thanks for your interest in helping make NetBox better. I'm moving this issue along to `needs owner` so that a developer with spare capacity can pick it up.
adam commented 2025-12-29 20:45:56 +01:00
Author
Owner
Copy Link

@jeffgdotorg commented on GitHub (May 31, 2024):

Tagging @doxic here as somebody who gave a 👍 to this issue and also took the time to ask for a priority bump in a separate channel. At the moment I cannot promise when we might get this FR scheduled, given the existing volume of planned work for the 4.1 release. Your best shot for moving the needle is to comment with the particulars of your use case that make it especially important to you, with the aim of convincing a developer with the necessary skills and capacity to take it up. Viel Glück!

@jeffgdotorg commented on GitHub (May 31, 2024): Tagging @doxic here as somebody who gave a 👍 to this issue and also took the time to ask for a priority bump in a separate channel. At the moment I cannot promise when we might get this FR scheduled, given the existing volume of planned work for the 4.1 release. Your best shot for moving the needle is to comment with the particulars of your use case that make it especially important to you, with the aim of convincing a developer with the necessary skills and capacity to take it up. Viel Glück!
adam commented 2025-12-29 20:45:56 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Aug 30, 2024):

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 (Aug 30, 2024): 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:45:56 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Oct 10, 2024):

Closing this as stale.

@jeremystretch commented on GitHub (Oct 10, 2024): Closing this as stale.
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 complexity: medium 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#9121
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?