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

Enable the device to which a module is assigned to be changed #8620

New Issue
Closed
opened 2025-12-29 20:38:59 +01:00 by adam · 6 comments
adam commented 2025-12-29 20:38:59 +01:00
Owner
Copy Link

Originally created by @francesco-noc on GitHub (Sep 15, 2023).

NetBox version

v3.6.1

Feature type

Change to existing functionality

Proposed functionality

Enable the device to which the module is assigned to be changed, as for inventory items.
This is not really a functionality, but more of an adaptation.
In the ModuleForm class, change self.fields['device'].disabled from True to False.

Use case

It may happen that a module (as well as an inventory item) is moved from one device to another and it would be useful not to have to delete and recreate it.

Database changes

No response

External dependencies

No response

Originally created by @francesco-noc on GitHub (Sep 15, 2023). ### NetBox version v3.6.1 ### Feature type Change to existing functionality ### Proposed functionality Enable the device to which the module is assigned to be changed, as for inventory items. This is not really a functionality, but more of an adaptation. In the ModuleForm class, change self.fields['device'].disabled from True to False. ### Use case It may happen that a module (as well as an inventory item) is moved from one device to another and it would be useful not to have to delete and recreate it. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: featurestatus: duplicate labels 2025-12-29 20:38:59 +01:00
adam closed this issue 2025-12-29 20:38:59 +01:00
adam commented 2025-12-29 20:39:00 +01:00
Author
Owner
Copy Link

@BackblazeJeremy commented on GitHub (Nov 9, 2023):

Moving inventory items from one device to another is a common occurrence for us. We often move NICs and storage drives between hosts as hardware is repaired, decommissioned, or repurposed. Having the ability to re-assign inventory items would be immensely useful to keep track of things more easily.

@BackblazeJeremy commented on GitHub (Nov 9, 2023): Moving inventory items from one device to another is a common occurrence for us. We often move NICs and storage drives between hosts as hardware is repaired, decommissioned, or repurposed. Having the ability to re-assign inventory items would be immensely useful to keep track of things more easily.
adam commented 2025-12-29 20:39:00 +01:00
Author
Owner
Copy Link

@francesco-noc commented on GitHub (Nov 10, 2023):

Exactly. We have about a thousand network devices and it is a common occurrence for modules as well.

@francesco-noc commented on GitHub (Nov 10, 2023): Exactly. We have about a thousand network devices and it is a common occurrence for modules as well.
adam commented 2025-12-29 20:39:00 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Feb 9, 2024):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Feb 9, 2024): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. **Do not** attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
adam commented 2025-12-29 20:39:00 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Mar 12, 2024):

A note for anyone who would like to tackle this implementation: Bear in mind that any components assigned to the module will need to be updated as well, as will the component counts of the former and new device.

@jeremystretch commented on GitHub (Mar 12, 2024): A note for anyone who would like to tackle this implementation: Bear in mind that any components assigned to the module will need to be updated as well, as will the component counts of the former and new device.
adam commented 2025-12-29 20:39:01 +01:00
Author
Owner
Copy Link

@francesco-noc commented on GitHub (Mar 12, 2024):

Hi @jeremystretch , as you suggested I did a more detailed feature request and I'm sorry, maybe this issue could be closed.
Anyway I proposed an implementation that destroy and recreate components when the module is edited.

@francesco-noc commented on GitHub (Mar 12, 2024): Hi @jeremystretch , as you suggested I did a [more detailed feature request](https://github.com/netbox-community/netbox/issues/15289) and I'm sorry, maybe this issue could be closed. Anyway I proposed [an implementation](https://github.com/netbox-community/netbox/compare/develop...francesco-noc:netbox:13779-change-device-to-module) that destroy and recreate components when the module is edited.
adam commented 2025-12-29 20:39:01 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Mar 12, 2024):

Ok, thanks. I'm going to close this one as a duplicate of #15289.

@jeremystretch commented on GitHub (Mar 12, 2024): Ok, thanks. I'm going to close this one as a duplicate of #15289.
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: duplicate 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#8620
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?