Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Render Config Contexts as YAML in GUI #3313

Closed
tyler-8 opened this issue Jul 1, 2019 · 0 comments · Fixed by #4011
Closed

Render Config Contexts as YAML in GUI #3313

tyler-8 opened this issue Jul 1, 2019 · 0 comments · Fixed by #4011
Labels
status: accepted This issue has been accepted for implementation type: feature Introduction of new functionality to the application

Comments

@tyler-8
Copy link
Contributor

tyler-8 commented Jul 1, 2019

Environment

  • Python version: 3.6.8
  • NetBox version: 2.5.13

Proposed Functionality

When creating/viewing configuration contexts via the Netbox GUI, allow for using YAML instead of JSON.

Use Case

YAML is more human readable and easier to type/format when manually editing. Since YAML is a superset of JSON, the API would still use JSON and the storage would still be done as JSON - this would purely be for frontend rendering.

Database Changes

N/A

External Dependencies

Likely one of these:

  • ruamel.yaml
  • pyyaml
@jeremystretch jeremystretch added status: accepted This issue has been accepted for implementation type: feature Introduction of new functionality to the application labels Oct 17, 2019
jeremystretch added a commit that referenced this issue Feb 3, 2020
Fixes #3313: YAML-format the config context in the GUI
jeremystretch added a commit that referenced this issue Feb 3, 2020
@lock lock bot locked as resolved and limited conversation to collaborators May 5, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
status: accepted This issue has been accepted for implementation type: feature Introduction of new functionality to the application
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants