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

Expose modules adopt_components and replicate_components via the API #11497

New Issue
Open
opened 2025-12-29 21:46:02 +01:00 by adam · 1 comment
adam commented 2025-12-29 21:46:02 +01:00
Owner
Copy Link

Originally created by @TheFlyingCorpse on GitHub (Aug 18, 2025).

NetBox version

v4.2.6

Feature type

Change to existing functionality

Proposed functionality

Expose «adopt_components» and «replicate_components» via the API, existing functionality already present in the Web GUI.

I found an old issue #10925 which ended up closed before merged which could have resolved this.

Use case

Helping to adapt the full Netbox model for environments with existing devices and cables.

For those with large environments that don’t want to reconnect thousands of cables, please expand so the API can expose these parameters, or allow us to submit a PR for it.

Database changes

No schema changes required.

External dependencies

None.

Originally created by @TheFlyingCorpse on GitHub (Aug 18, 2025). ### NetBox version v4.2.6 ### Feature type Change to existing functionality ### Proposed functionality Expose «adopt_components» and «replicate_components» via the API, existing functionality already present in the Web GUI. I found an old issue #10925 which ended up closed before merged which could have resolved this. ### Use case Helping to adapt the full Netbox model for environments with existing devices and cables. For those with large environments that don’t want to reconnect thousands of cables, please expand so the API can expose these parameters, or allow us to submit a PR for it. ### Database changes No schema changes required. ### External dependencies None.
adam commented 2025-12-29 21:46:03 +01:00
Author
Owner
Copy Link

@CADbloke commented on GitHub (Nov 3, 2025):

This would certainly ease the adoption of the move to model SPFs as Modules with an Interface instead of just as raw interfaces as per https://netboxlabs.com/blog/sfp-modeling-modules-over-inventory-items/
I presume we're not the only ones trying to figure out a workflow towwards this.
... or am I misunderstanding and the default is to adopt components?

@CADbloke commented on GitHub (Nov 3, 2025): This would certainly ease the adoption of the move to model SPFs as Modules with an Interface instead of just as raw interfaces as per https://netboxlabs.com/blog/sfp-modeling-modules-over-inventory-items/ I presume we're not the only ones trying to figure out a workflow towwards this. ... or am I misunderstanding and the default is to adopt components?
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 complexity: medium needs milestone netbox status: backlog 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#11497
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?