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

Remove Manufacturer constraint on Platform to Device assignment #10847

New Issue
Closed
opened 2025-12-29 21:36:40 +01:00 by adam · 1 comment
adam commented 2025-12-29 21:36:40 +01:00
Owner
Copy Link

Originally created by @empusas on GitHub (Mar 5, 2025).

Proposed Changes

Currently, NetBox imposes a constraint that a Platform can only be assigned to a Device if the Manufacturer matches or if no Manufacturer is set on the Platform.

While this restriction may be reasonable for most network devices (about 95% of cases), it proves impractical for nearly everything else.

The only apparent purpose of this limitation seems to be restricting options in the UI.

Justification

As mentioned above, for about 95% of network devices, there may be a 1:1 relationship between the hardware manufacturer and the software provider.

However, in the compute world, this is not the case. Your server hardware might be from Dell or Lenovo, while the operating system could be provided by Red Hat or Microsoft.

Currently, the only workaround is to remove the Manufacturer from the Platform, which technically works but also removes valuable information that could be useful in other scenarios.

And to the argument that “NetBox is primarily for networking, not compute or storage,” I would counter:
How can you achieve a comprehensive view of infrastructure if NetBox only includes network data for cabling and IPAM, but lacks visibility into compute and storage?

Impact

The only impact I can see right now is that all Platforms will be listed in the UI dropdown. However, I’m happy to learn about any other potential impacts.

Originally created by @empusas on GitHub (Mar 5, 2025). ### Proposed Changes Currently, NetBox imposes a constraint that a Platform can only be assigned to a Device if the Manufacturer matches or if no Manufacturer is set on the Platform. While this restriction may be reasonable for most network devices (about 95% of cases), it proves impractical for nearly everything else. The only apparent purpose of this limitation seems to be restricting options in the UI. ### Justification As mentioned above, for about 95% of network devices, there may be a 1:1 relationship between the hardware manufacturer and the software provider. However, in the compute world, this is not the case. Your server hardware might be from Dell or Lenovo, while the operating system could be provided by Red Hat or Microsoft. Currently, the only workaround is to remove the Manufacturer from the Platform, which technically works but also removes valuable information that could be useful in other scenarios. And to the argument that “NetBox is primarily for networking, not compute or storage,” I would counter: How can you achieve a comprehensive view of infrastructure if NetBox only includes network data for cabling and IPAM, but lacks visibility into compute and storage? ### Impact The only impact I can see right now is that all Platforms will be listed in the UI dropdown. However, I’m happy to learn about any other potential impacts.
adam closed this issue 2025-12-29 21:36:40 +01:00
adam commented 2025-12-29 21:36:41 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Mar 5, 2025):

Deprecation issues are for tracking the removal of functionality from the application, which does not apply here. Please resubmit this as a feature request.

@jeremystretch commented on GitHub (Mar 5, 2025): Deprecation issues are for tracking the removal of functionality from the application, which does not apply here. Please resubmit this as a [feature request](https://github.com/netbox-community/netbox/issues/new?template=01-feature_request.yaml).
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#10847
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?