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

Update devices connected to a device type when changes are made to a device-type #9694

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

Originally created by @RemcoVroman on GitHub (May 17, 2024).

NetBox version

v3.7.2

Feature type

Data model extension

Proposed functionality

Update devices connected to a device type when changes are made to a device-type.

Use case

For example: when I add power ports to a device-type because we need to go from two to four power ports. So I add the power ports to the device type and all new devices will get the two extra power ports. But I need to do add manualy the two power ports to all devices that are of the same device type.

Database changes

update statements will be required after a device-type is changed

External dependencies

N/A

Originally created by @RemcoVroman on GitHub (May 17, 2024). ### NetBox version v3.7.2 ### Feature type Data model extension ### Proposed functionality Update devices connected to a device type when changes are made to a device-type. ### Use case For example: when I add power ports to a device-type because we need to go from two to four power ports. So I add the power ports to the device type and all new devices will get the two extra power ports. But I need to do add manualy the two power ports to all devices that are of the same device type. ### Database changes update statements will be required after a device-type is changed ### External dependencies N/A
adam added the type: feature label 2025-12-29 21:21:02 +01:00
adam closed this issue 2025-12-29 21:21:02 +01:00
adam commented 2025-12-29 21:21:03 +01:00
Author
Owner
Copy Link

@arthanson commented on GitHub (May 17, 2024):

I think this could get tricky or confusing, we would only want to do additions as deletions would be dangerous, also if done it should probably be a dialog showing what would change (like delete) and a confirmation.

@arthanson commented on GitHub (May 17, 2024): I think this could get tricky or confusing, we would only want to do additions as deletions would be dangerous, also if done it should probably be a dialog showing what would change (like delete) and a confirmation.
adam commented 2025-12-29 21:21:03 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 17, 2024):

This has been proposed in the past and rejected because it is not possible for NetBox to interpret the intended behavior of every possible scenario. (Consider, for instance, the implications of renaming or removing a device component.) Instead, please use NetBox's ability to bulk create components on multiple devices to achieve this functionality in a predictable and safe manner.

@jeremystretch commented on GitHub (May 17, 2024): This has been [proposed](https://github.com/netbox-community/netbox/issues/3233) in the past and rejected because it is not possible for NetBox to interpret the intended behavior of every possible scenario. (Consider, for instance, the implications of renaming or removing a device component.) Instead, please use NetBox's ability to bulk create components on multiple devices to achieve this functionality in a predictable and safe manner.
adam commented 2025-12-29 21:21:03 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 17, 2024):

Here's an example:

screenshot

@jeremystretch commented on GitHub (May 17, 2024): Here's an example: ![screenshot](https://github.com/netbox-community/netbox/assets/13487278/df60cb7d-3bf9-438b-ba74-ba1ef067d8d6)
adam commented 2025-12-29 21:21:04 +01:00
Author
Owner
Copy Link

@RemcoVroman commented on GitHub (May 28, 2024):

Hi Jeremy, I do not agree with youre statement about not being able to predict every behaviour. You might have a look at Zabbix monitoring tool, there are templates (is equal to device-types in Netbox) being used. Every device connected to a template is being monitored in the same way. Is the template changed, it will apply to all devices connected to the template.
Having said that, I think it is the responsibility of a Netbox administrator to properly administer the device-types and create multiple device-types for the same system with serveral possible configurations.
Please take this in concideration. If you want a Zabbix demo with the template use, I'm willing to provide that.
Best regards,
Remco

@RemcoVroman commented on GitHub (May 28, 2024): Hi Jeremy, I do not agree with youre statement about not being able to predict every behaviour. You might have a look at Zabbix monitoring tool, there are templates (is equal to device-types in Netbox) being used. Every device connected to a template is being monitored in the same way. Is the template changed, it will apply to all devices connected to the template. Having said that, I think it is the responsibility of a Netbox administrator to properly administer the device-types and create multiple device-types for the same system with serveral possible configurations. Please take this in concideration. If you want a Zabbix demo with the template use, I'm willing to provide that. Best regards, Remco
adam commented 2025-12-29 21:21:04 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 28, 2024):

You're free to disagree, and you're free to fork and modify the code base as you see fit, and be responsible for those changes. However your proposed change has already been considered and rejected, and will not be implemented in the core product.

@jeremystretch commented on GitHub (May 28, 2024): You're free to disagree, and you're free to fork and modify the code base as you see fit, and be responsible for those changes. However your proposed change has already been considered and rejected, and will not be implemented in the core product.
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 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#9694
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?