-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Comments
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. |
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. |
For simple arbitrary key/value store, see the JSONB data type I just mentioned on #1349. :) |
@puck v2.2 will require PostgreSQL 9.4+ to support JSONB anyway (for storing report data), so that's a very appealing solution. |
Blocked by #3294 |
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. |
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. |
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. |
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.
The text was updated successfully, but these errors were encountered: