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.

Sign up for GitHub

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

Jump to bottom

Allow Change of Default For Config-Context YAML JSON toggle mode #4421

Closed
a31amit opened this issue Mar 29, 2020 · 3 comments
Closed

Allow Change of Default For Config-Context YAML JSON toggle mode #4421

a31amit opened this issue Mar 29, 2020 · 3 comments
Assignees
@jeremystretch
Labels
status: accepted This issue has been accepted for implementation type: feature Introduction of new functionality to the application

Comments

@a31amit
Copy link

a31amit commented Mar 29, 2020

Environment

  • Python version: 3.6
  • NetBox version: 2.7 latest

Proposed Functionality

Please allow a Configuration option for Default Setting Config-Context YAML JSON toggle mode.

Use Case

This will help netbox admins and users to set the preferred mode for their userbase

Database Changes

None

External Dependencies

None
@DanSheps
Copy link
Member

Similar to #1426 and would be blocked by #3294, I can get behind this however, once #3294 is implemented.

@jeremystretch jeremystretch added status: blocked Another issue or external requirement is preventing implementation type: feature Introduction of new functionality to the application labels Mar 30, 2020
@a31amit
Copy link
Author

a31amit commented Mar 30, 2020

While this can be a per-user basis, adding a new default global configuration options would also help to change global behaviors. currently, default is JSON without any option to configure in configuration.py.

@jeremystretch
Copy link
Member

A per-user toggle for this would be sufficient. We want to avoid clogging up the global configuration with niche toggles.

@jeremystretch jeremystretch added status: accepted This issue has been accepted for implementation and removed status: blocked Another issue or external requirement is preventing implementation labels Apr 24, 2020
@jeremystretch jeremystretch self-assigned this Apr 24, 2020
@jeremystretch jeremystretch mentioned this issue May 6, 2020
Merged
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 11, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@jeremystretch jeremystretch

Labels
status: accepted This issue has been accepted for implementation type: feature Introduction of new functionality to the application
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@a31amit @DanSheps @jeremystretch