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

ModuleBay positions are more than just numeric #8520

New Issue
Closed
opened 2025-12-29 20:37:43 +01:00 by adam · 2 comments
adam commented 2025-12-29 20:37:43 +01:00
Owner
Copy Link

Originally created by @pv2b on GitHub (Aug 27, 2023).

Change Type

Correction

Area

Other

Proposed Changes

The documentation for the ModelBay model describes the position field as such:

The numeric position in which this module bay is situated. For example, this would be the number assigned to a slot within a chassis-based switch.

A reader might misinterpret the word "numeric" to mean only integers are permitted in this field, when in fact, any string is permitted.

This is in fact useful when modelling devices such as the HPE ProCurve 5400 series chassis-based switches that label their module slots as A, B, C, etc.

Therefore I suggest substituting the word "alphanumeric" for "numeric", to avoid confusion.

Originally created by @pv2b on GitHub (Aug 27, 2023). ### Change Type Correction ### Area Other ### Proposed Changes The [documentation for the ModelBay model](https://docs.netbox.dev/en/stable/models/dcim/modulebay/) describes the `position` field as such: > The numeric position in which this module bay is situated. For example, this would be the number assigned to a slot within a chassis-based switch. A reader might misinterpret the word "numeric" to mean only integers are permitted in this field, when in fact, any string is permitted. This is in fact useful when modelling devices such as the HPE ProCurve 5400 series chassis-based switches that label their module slots as A, B, C, etc. Therefore I suggest substituting the word "alphanumeric" for "numeric", to avoid confusion.
adam added the type: documentationpending closure labels 2025-12-29 20:37:43 +01:00
adam closed this issue 2025-12-29 20:37:43 +01:00
adam commented 2025-12-29 20:37:44 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Nov 26, 2023):

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. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Nov 26, 2023): 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. **Do not** attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
adam commented 2025-12-29 20:37:44 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Dec 26, 2023):

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.

@github-actions[bot] commented on GitHub (Dec 26, 2023): 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.
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 pending closure type: documentation
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#8520
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?