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 an option to adopt existing DeviceComponents when installing modules #6437

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

Originally created by @kkthxbye-code on GitHub (May 2, 2022).

Originally assigned to: @kkthxbye-code on GitHub.

NetBox version

v3.2.2

Feature type

Change to existing functionality

Proposed functionality

Add an option to adopt existing DeviceComponents when installing modules. The option would change the module of all DeviceComponents on the target device with the same name as the component being added by the module.

Use case

Making it easier to migrate to using modules for devices with manually added DeviceComponents.

Database changes

None.

External dependencies

None.

Originally created by @kkthxbye-code on GitHub (May 2, 2022). Originally assigned to: @kkthxbye-code on GitHub. ### NetBox version v3.2.2 ### Feature type Change to existing functionality ### Proposed functionality Add an option to adopt existing DeviceComponents when installing modules. The option would change the module of all DeviceComponents on the target device with the same name as the component being added by the module. ### Use case Making it easier to migrate to using modules for devices with manually added DeviceComponents. ### Database changes None. ### External dependencies None.
adam added the status: acceptedtype: feature labels 2025-12-29 19:40:43 +01:00
adam closed this issue 2025-12-29 19:40:43 +01:00
adam commented 2025-12-29 19:40:44 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 3, 2022):

I like it. We should end up with four possible conditions depending on which boxes are checked:

Replicate Adopt Result
- - No components get created or updated
x - New components get created but existing components are unmodified
- x Existing components with matching names are assigned to the module, but no new components are created
x x If a matching component exists, assign it to the module; otherwise create a new one
@jeremystretch commented on GitHub (May 3, 2022): I like it. We should end up with four possible conditions depending on which boxes are checked: | Replicate | Adopt | Result | |---|---|---| | - | - | No components get created or updated | | x | - | New components get created but existing components are unmodified | | - | x | Existing components with matching names are assigned to the module, but no new components are created | | x | x | If a matching component exists, assign it to the module; otherwise create a new one |
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#6437
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?