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

Unused status in choice field for ipaddress #2365

New Issue
Closed
opened 2025-12-29 17:25:19 +01:00 by adam · 1 comment
adam commented 2025-12-29 17:25:19 +01:00
Owner
Copy Link

Originally created by @kobayashi on GitHub (Feb 12, 2019).

Environment

  • Python version:
  • NetBox version:
    N/A

Proposed Functionality

I would like to add IPADDRESS_STATUS_UNUSED to IPADDRESS_CHOICES.

Like followings in ipam/constants.py.

# IP address statuses
IPADDRESS_STATUS_UNUSED = 0    # <- add this line
IPADDRESS_STATUS_ACTIVE = 1
IPADDRESS_STATUS_RESERVED = 2
IPADDRESS_STATUS_DEPRECATED = 3
IPADDRESS_STATUS_DHCP = 5
IPADDRESS_STATUS_CHOICES = (
    (IPADDRESS_STATUS_UNUSED, 'Unused'),  # <- add this line
    (IPADDRESS_STATUS_ACTIVE, 'Active'),
    (IPADDRESS_STATUS_RESERVED, 'Reserved'),
    (IPADDRESS_STATUS_DEPRECATED, 'Deprecated'),
    (IPADDRESS_STATUS_DHCP, 'DHCP')
)

Assigned as 0 is easy to set the color as default.

# Bootstrap CSS classes
STATUS_CHOICE_CLASSES = {
    0: 'default',
    1: 'primary',
    2: 'info',
    3: 'danger',
    4: 'warning',
    5: 'success',
}

Use Case

In my case, there are several managed ipaddresses which are not active and not reserved for something. unused is better choice for these ipaddresses.

Database Changes

No

External Dependencies

No

Originally created by @kobayashi on GitHub (Feb 12, 2019). <!-- NOTE: 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: <!-- Example: 3.5.4 --> * NetBox version: <!-- Example: 2.3.6 --> N/A <!-- Describe in detail the new functionality you are proposing. Include any specific changes to work flows, data models, or the user interface. --> ### Proposed Functionality I would like to add `IPADDRESS_STATUS_UNUSED` to `IPADDRESS_CHOICES`. Like followings in ipam/constants.py. ``` # IP address statuses IPADDRESS_STATUS_UNUSED = 0 # <- add this line IPADDRESS_STATUS_ACTIVE = 1 IPADDRESS_STATUS_RESERVED = 2 IPADDRESS_STATUS_DEPRECATED = 3 IPADDRESS_STATUS_DHCP = 5 IPADDRESS_STATUS_CHOICES = ( (IPADDRESS_STATUS_UNUSED, 'Unused'), # <- add this line (IPADDRESS_STATUS_ACTIVE, 'Active'), (IPADDRESS_STATUS_RESERVED, 'Reserved'), (IPADDRESS_STATUS_DEPRECATED, 'Deprecated'), (IPADDRESS_STATUS_DHCP, 'DHCP') ) ``` Assigned as 0 is easy to set the color as default. ``` # Bootstrap CSS classes STATUS_CHOICE_CLASSES = { 0: 'default', 1: 'primary', 2: 'info', 3: 'danger', 4: 'warning', 5: 'success', } ``` <!-- 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 In my case, there are several managed ipaddresses which are not active and not reserved for something. `unused` is better choice for these ipaddresses. <!-- 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 No <!-- 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 No
adam closed this issue 2025-12-29 17:25:20 +01:00
adam commented 2025-12-29 17:25:20 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Feb 12, 2019):

The philosophical approach taken by NetBox is that if an IP address is unused, it should not be defined.

@jeremystretch commented on GitHub (Feb 12, 2019): The philosophical approach taken by NetBox is that if an IP address is unused, it should not be defined.
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
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#2365
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?