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

[PR #2793] [MERGED] Clarify how chassis-based switches/routers are supposed to be modelled #12437

New Issue
Closed
opened 2025-12-29 22:21:35 +01:00 by adam · 0 comments
adam commented 2025-12-29 22:21:35 +01:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/netbox-community/netbox/pull/2793
Author: @candlerb
Created: 1/17/2019
Status: ✅ Merged
Merged: 2/6/2019
Merged by: @jeremystretch

Base: develop ← Head: candlerb/doc-inventory

📝 Commits (1)

  • 9991985 Clarify how chassis-based switches and routers are supposed to be modelled

📊 Changes

1 file changed (+9 additions, -1 deletions)

View changed files

📝 docs/core-functionality/devices.md (+9 -1)

📄 Description

Fixes:

It is a frequent misconception that Device Bays (parent/child) are what you'd use for line cards in a chassis switch or router - e.g. #2752, #2234, #2145, #1760, #1205, #970, #823, #636, #337, various group postings.

This patch expands the documentation to explain how these should be modelled instead.

(Could also link to #824 but I have not done that)

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/netbox-community/netbox/pull/2793 **Author:** [@candlerb](https://github.com/candlerb) **Created:** 1/17/2019 **Status:** ✅ Merged **Merged:** 2/6/2019 **Merged by:** [@jeremystretch](https://github.com/jeremystretch) **Base:** `develop` ← **Head:** `candlerb/doc-inventory` --- ### 📝 Commits (1) - [`9991985`](https://github.com/netbox-community/netbox/commit/9991985170d816d7a5fd5a8bb16299a821256ea9) Clarify how chassis-based switches and routers are supposed to be modelled ### 📊 Changes **1 file changed** (+9 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `docs/core-functionality/devices.md` (+9 -1) </details> ### 📄 Description ### Fixes: It is a frequent misconception that Device Bays (parent/child) are what you'd use for line cards in a chassis switch or router - e.g. #2752, #2234, #2145, #1760, #1205, #970, #823, #636, #337, various group postings. This patch expands the documentation to explain how these should be modelled instead. (Could also link to #824 but I have not done that) --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
adam added the pull-request label 2025-12-29 22:21:35 +01:00
adam closed this issue 2025-12-29 22:21:35 +01:00
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 pull-request
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#12437
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?