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

Support for creation of ConfigContexts using YAML-formatted data #3377

New Issue
Closed
opened 2025-12-29 18:28:31 +01:00 by adam · 5 comments
adam commented 2025-12-29 18:28:31 +01:00
Owner
Copy Link

Originally created by @jeremystretch on GitHub (Feb 21, 2020).

Environment

  • Python version: 3.6.9
  • NetBox version: 2.7.7

Proposed Functionality

Implement the ability to create and edit config context data in YAML format. (Currently only JSON is available.) This follows #3313, which enabled the display of data in YAML format.

Use Case

Offers convenience for users who have data already in YAML format, and achieves parity with the current ability to display data in either YAML or JSON.

Database Changes

None

External Dependencies

None

Originally created by @jeremystretch on GitHub (Feb 21, 2020). ### Environment * Python version: 3.6.9 * NetBox version: 2.7.7 ### Proposed Functionality Implement the ability to create and edit config context data in YAML format. (Currently only JSON is available.) This follows #3313, which enabled the display of data in YAML format. ### Use Case Offers convenience for users who have data already in YAML format, and achieves parity with the current ability to display data in either YAML or JSON. ### Database Changes None ### External Dependencies None
adam added the type: featurestatus: needs ownerpending closure labels 2025-12-29 18:28:31 +01:00
adam closed this issue 2025-12-29 18:28:31 +01:00
adam commented 2025-12-29 18:28:32 +01:00
Author
Owner
Copy Link

@sdktr commented on GitHub (Feb 21, 2020):

What to do with fields that are a superset of JSON? Like comments and anchor options?

@sdktr commented on GitHub (Feb 21, 2020): What to do with fields that are a superset of JSON? Like comments and anchor options?
adam commented 2025-12-29 18:28:33 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Feb 21, 2020):

The data is still stored as JSON in the database, so we either strip them silently or fail on validation.

@jeremystretch commented on GitHub (Feb 21, 2020): The data is still stored as JSON in the database, so we either strip them silently or fail on validation.
adam commented 2025-12-29 18:28:33 +01:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (Mar 6, 2020):

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.

@stale[bot] commented on GitHub (Mar 6, 2020): 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 18:28:33 +01:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (Sep 7, 2020):

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.

@stale[bot] commented on GitHub (Sep 7, 2020): 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 18:28:34 +01:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (Sep 23, 2020):

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.

@stale[bot] commented on GitHub (Sep 23, 2020): 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#3377
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?