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

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

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

Originally created by @a31amit on GitHub (Mar 29, 2020).

Originally assigned to: @jeremystretch on GitHub.

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

Originally created by @a31amit on GitHub (Mar 29, 2020). Originally assigned to: @jeremystretch on GitHub. <!-- NOTE: IF YOUR ISSUE DOES NOT FOLLOW THIS TEMPLATE, IT WILL BE CLOSED. This form is only for proposing specific new features or enhancements. If you have a general idea or question, please post to our mailing list instead of opening an issue: https://groups.google.com/forum/#!forum/netbox-discuss NOTE: Due to an excessive backlog of feature requests, we are not currently accepting any proposals which significantly extend NetBox's feature scope. Please describe the environment in which you are running NetBox. Be sure that you are running an unmodified instance of the latest stable release before submitting a bug report. --> ### Environment * Python version: 3.6 <!-- Example: 3.6.9 --> * NetBox version: 2.7 latest <!-- Example: 2.7.3 --> <!-- Describe in detail the new functionality you are proposing. Include any specific changes to work flows, data models, or the user interface. --> ### Proposed Functionality Please allow a Configuration option for Default Setting Config-Context YAML JSON toggle mode. <!-- Convey an example use case for your proposed feature. Write from the perspective of a NetBox user who would benefit from the proposed functionality and describe how. ---> ### Use Case This will help netbox admins and users to set the preferred mode for their userbase <!-- Note any changes to the database schema necessary to support the new feature. For example, does the proposal require adding a new model or field? (Not all new features require database changes.) ---> ### Database Changes None <!-- List any new dependencies on external libraries or services that this new feature would introduce. For example, does the proposal require the installation of a new Python package? (Not all new features introduce new dependencies.) --> ### External Dependencies None
adam added the status: acceptedtype: feature labels 2025-12-29 18:29:37 +01:00
adam closed this issue 2025-12-29 18:29:37 +01:00
adam commented 2025-12-29 18:29:37 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Mar 30, 2020):

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

@DanSheps commented on GitHub (Mar 30, 2020): Similar to #1426 and would be blocked by #3294, I can get behind this however, once #3294 is implemented.
adam commented 2025-12-29 18:29:37 +01:00
Author
Owner
Copy Link

@a31amit commented on GitHub (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.

@a31amit commented on GitHub (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.
adam commented 2025-12-29 18:29:37 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Mar 30, 2020):

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

@jeremystretch commented on GitHub (Mar 30, 2020): A per-user toggle for this would be sufficient. We want to avoid clogging up the global configuration with niche toggles.
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 status: accepted 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#3517
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?