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

Add Bulk Edit to ConfigContext #2490

Closed
bdlamprecht opened this issue Oct 5, 2018 · 0 comments
Closed

Add Bulk Edit to ConfigContext #2490

bdlamprecht opened this issue Oct 5, 2018 · 0 comments
Labels
status: accepted This issue has been accepted for implementation type: feature Introduction of new functionality to the application

Comments

@bdlamprecht
Copy link
Contributor

bdlamprecht commented Oct 5, 2018

Environment

  • Python version: 3.6
  • NetBox version: 2.4.5

Proposed Functionality

Similar to the way that you can bulk edit devices, device-types, ip-addresses, prefixes and others, I'd like to see if the same functionality can be added to config-contexts.

The only values that immediately make sense to enable bulk editing are weight and active. I could see the potential to include assignments as well, but I have a feeling that could be opening a "can of worms" that we don't want to deal with.

Use Case

As an example, this is a screenshot of my config-contexts in the WebUI:

config-contexts

Suppose I want to change the weight on all of them due to a change in structure, I would have to manually edit each one. If a bulk edit were enabled, this could be done much easier.

As another example, suppose I'm trying to resolve an issue with the way config-contexts are being rendered on a device, being able to bulk edit them to temporarily change the active status would be extremely helpful.

Database Changes

I don't believe there should be any as config-contexts are a primary model.

External Dependencies

None.

@jeremystretch jeremystretch added status: accepted This issue has been accepted for implementation type: feature Introduction of new functionality to the application labels Oct 9, 2018
@lock lock bot locked as resolved and limited conversation to collaborators Jan 16, 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

No branches or pull requests

2 participants