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

Add platform to device type #6622

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

Originally created by @powerscooter on GitHub (Jul 3, 2022).

Originally assigned to: @kkthxbye-code on GitHub.

NetBox version

v3.2.3

Feature type

New functionality

Proposed functionality

Hello,

is it possible to add the point "management - platform" to the device type, so that this is inherited by the device as soon as it is created?

Use case

We use this option to document the running system of the devices. For example: Juniper -> Junos

Since this is the same for each device type, you could save the step of entering it manually.
Another point would be that less mistakes are made when entering data.

Database changes

No response

External dependencies

No response

Originally created by @powerscooter on GitHub (Jul 3, 2022). Originally assigned to: @kkthxbye-code on GitHub. ### NetBox version v3.2.3 ### Feature type New functionality ### Proposed functionality Hello, is it possible to add the point "management - platform" to the device type, so that this is inherited by the device as soon as it is created? ### Use case We use this option to document the running system of the devices. For example: Juniper -> Junos Since this is the same for each device type, you could save the step of entering it manually. Another point would be that less mistakes are made when entering data. ### Database changes _No response_ ### External dependencies _No response_
adam added the status: acceptedtype: feature labels 2025-12-29 19:43:15 +01:00
adam closed this issue 2025-12-29 19:43:15 +01:00
adam commented 2025-12-29 19:43:15 +01:00
Author
Owner
Copy Link

@shatt79 commented on GitHub (Jul 19, 2022):

Could something like this be expanded out to modules as well? I'd love to be able to only install certain modules in specific devices. Eg, only modules in the ASR9K family can be installed in an ASR9K platform/device.

@shatt79 commented on GitHub (Jul 19, 2022): Could something like this be expanded out to modules as well? I'd love to be able to only install certain modules in specific devices. Eg, only modules in the ASR9K family can be installed in an ASR9K platform/device.
adam commented 2025-12-29 19:43:15 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jul 27, 2022):

I think it makes sense to add an optional "default platform" field to the DeviceType model. If set, this will be automatically populated on instantiated devices, however (as with components) it can still be modified afterward.

Could something like this be expanded out to modules as well?

Possibly, but please open a separate FR if that's something you'd like to propose.

@jeremystretch commented on GitHub (Jul 27, 2022): I think it makes sense to add an optional "default platform" field to the DeviceType model. If set, this will be automatically populated on instantiated devices, however (as with components) it can still be modified afterward. > Could something like this be expanded out to modules as well? Possibly, but please open a separate FR if that's something you'd like to propose.
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 status: accepted 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#6622
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?