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

Allow default statuses to be customised #1426

Closed
cmccallan opened this issue Aug 14, 2017 · 8 comments
Closed

Allow default statuses to be customised #1426

cmccallan opened this issue Aug 14, 2017 · 8 comments
Labels
pending closure Requires immediate attention to avoid being closed for inactivity status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation type: feature Introduction of new functionality to the application

Comments

@cmccallan
Copy link

Issue type: Feature Request

Python version:
NetBox version:

Currently when new IP addresses, Prefixes and VLANs are created their Status is defaulted to Active. This sometimes leads to issues of Netbox no longer being a source of truth if someone creates an IP/prefix/vlan and doesn't know/realise that it needs to be set to Reserved until it is actually active.
What we'd ideally like to have is to be able to set Reserved to be the default, and then it can be changed to Active/Deprecated/DHCP when it is actually in that state. This would prevent having multiple IPs/prefixes/VLANs assigned Active that are not and improve reliability of our setup.

@jeremystretch
Copy link
Member

This is similar to #492 (and probably some others) in that it would require a mechanism for storing preferences for individual users. I'd like to implement a simple sort of key/value store for this (rather than continually extending a profile model). Need to look more into what would work best.

@jeremystretch jeremystretch added the type: feature Introduction of new functionality to the application label Aug 15, 2017
@cmccallan
Copy link
Author

Potential workaround could be making it a mandatory field and setting default to a null value? Might not be ideal but would prevent wrong provisioning if a user has to manually select a status.

@jeremystretch jeremystretch changed the title Allow default statuses to be customised. Allow default statuses to be customised Aug 15, 2017
@puck
Copy link

puck commented Aug 20, 2017

For simple arbitrary key/value store, see the JSONB data type I just mentioned on #1349. :)

@jeremystretch
Copy link
Member

@puck v2.2 will require PostgreSQL 9.4+ to support JSONB anyway (for storing report data), so that's a very appealing solution.

@jeremystretch jeremystretch added the status: accepted This issue has been accepted for implementation label Jan 26, 2018
@jeremystretch jeremystretch added status: blocked Another issue or external requirement is preventing implementation and removed status: accepted This issue has been accepted for implementation labels Jun 24, 2019
@jeremystretch
Copy link
Member

Blocked by #3294

@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 added status: under review Further discussion is needed to determine this issue's scope and/or implementation and removed status: accepted This issue has been accepted for implementation labels Jul 24, 2020
@jeremystretch
Copy link
Member

Rather than requiring the user to pick a specific default status (for this and numerous other objects), it might make more sense for NetBox to "remember" the last-chosen status used when creating/editing that type of object. This would work similarly to how NetBox remembers table column preferences for individual users.

@jeremystretch jeremystretch added status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation and removed status: under review Further discussion is needed to determine this issue's scope and/or implementation labels Sep 1, 2020
@stale
Copy link

stale bot commented Oct 16, 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 stale bot added the pending closure Requires immediate attention to avoid being closed for inactivity label Oct 16, 2020
@stale
Copy link

stale bot commented Oct 31, 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 stale bot closed this as completed Oct 31, 2020
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jan 30, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
pending closure Requires immediate attention to avoid being closed for inactivity status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation type: feature Introduction of new functionality to the application
Projects
None yet
Development

No branches or pull requests

3 participants