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

Support for marking module bays and device bays as disabled #11516

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

Originally created by @0lini on GitHub (Aug 21, 2025).

NetBox version

v4.3.6

Feature type

Data model extension

Proposed functionality

Currently, NetBox allows interfaces to be marked as disabled, which helps indicate that they are not available for use. It would be useful to have the same functionality for module and device bays, allowing them to be marked as disabled when they are unavailable, decommissioned, or reserved.

Use case

Devices can have module bays that physically exist, but are disabled in specific circumstances. An example of that is switches that disable ports based on the feature set used.

Database changes

No response

External dependencies

No response

Originally created by @0lini on GitHub (Aug 21, 2025). ### NetBox version v4.3.6 ### Feature type Data model extension ### Proposed functionality Currently, NetBox allows interfaces to be marked as disabled, which helps indicate that they are not available for use. It would be useful to have the same functionality for module and device bays, allowing them to be marked as disabled when they are unavailable, decommissioned, or reserved. ### Use case Devices can have module bays that physically exist, but are disabled in specific circumstances. An example of that is switches that disable ports based on the feature set used. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: featurenetboxneeds milestonestatus: backlogcomplexity: low labels 2025-12-29 21:46:18 +01:00
adam commented 2025-12-29 21:46:18 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 28, 2025):

Does it make more sense to introduce a boolean enabled field, or a status choice field with multiple options? Or both?

@jeremystretch commented on GitHub (Aug 28, 2025): Does it make more sense to introduce a boolean `enabled` field, or a `status` choice field with multiple options? Or both?
adam commented 2025-12-29 21:46:18 +01:00
Author
Owner
Copy Link

@0lini commented on GitHub (Aug 28, 2025):

For my use case, a boolean field would suffice. I can't currently think of a use case that would benefit from a status field, it would just increase complexity.

@0lini commented on GitHub (Aug 28, 2025): For my use case, a boolean field would suffice. I can't currently think of a use case that would benefit from a status field, it would just increase complexity.
adam commented 2025-12-29 21:46:19 +01:00
Author
Owner
Copy Link

@0lini commented on GitHub (Dec 14, 2025):

I created a working implementation using AI. If it helps, I can create a pull request containing it.

@0lini commented on GitHub (Dec 14, 2025): I created a working implementation using AI. If it helps, I can create a pull request containing it.
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 complexity: low needs milestone netbox status: backlog 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#11516
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?