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

Editing Device Type Does Not Cascade to Existing Devices #308

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

Originally created by @swickstrom on GitHub (Jul 29, 2016).

If you edit a Device Type (add new interfaces, remove a power outlet, update interface info, etc) it will not cascade to the existing devices using that Device Type.
If this is intended, would it be possible to have an OVERRIDE option to force the update to existing devices?
Also, there is no way to update existing outlets/interfaces/console port names/properties; only delete them. Could that functionality possibly be added?

Originally created by @swickstrom on GitHub (Jul 29, 2016). If you edit a `Device Type` (add new interfaces, remove a power outlet, update interface info, etc) it will not cascade to the existing devices using that `Device Type`. If this is intended, would it be possible to have an OVERRIDE option to force the update to existing devices? Also, there is no way to update existing outlets/interfaces/console port names/properties; only delete them. Could that functionality possibly be added?
adam closed this issue 2025-12-29 16:20:45 +01:00
adam commented 2025-12-29 16:20:46 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jul 29, 2016):

If you edit a Device Type (add new interfaces, remove a power outlet, update interface info, etc) it will not cascade to the existing devices using that Device Type.

Yep, this is intentional. It's called out in the docs.

Also, there is no way to update existing outlets/interfaces/console port names/properties; only delete them. Could that functionality possibly be added?

#353 was opened for this recently.

@jeremystretch commented on GitHub (Jul 29, 2016): > If you edit a Device Type (add new interfaces, remove a power outlet, update interface info, etc) it will not cascade to the existing devices using that Device Type. Yep, this is intentional. It's called out in [the docs](http://netbox.readthedocs.io/en/latest/data-model/dcim/#device-types). > Also, there is no way to update existing outlets/interfaces/console port names/properties; only delete them. Could that functionality possibly be added? #353 was opened for this recently.
adam commented 2025-12-29 16:20:46 +01:00
Author
Owner
Copy Link

@swickstrom commented on GitHub (Jul 29, 2016):

Apologies for my ignorance, could have easily been solved if I had RTFM...

@swickstrom commented on GitHub (Jul 29, 2016): Apologies for my ignorance, could have easily been solved if I had RTFM...
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#308
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?