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

Assign devices to rack from rack view #7372

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

Originally created by @fabi125 on GitHub (Dec 16, 2022).

NetBox version

v3.4.0

Feature type

New functionality

Proposed functionality

Allow racking an existing device from the rack view (in addition to being able to create a new device via that flow).

This can easily be achieved when modelling after the "Assign existing IP address to interface" flow. I'll put up a PR for it shortly.

Use case

This makes it a lot easier to rack existing devices when doing rack work.

Database changes

n/a

External dependencies

n/a

Originally created by @fabi125 on GitHub (Dec 16, 2022). ### NetBox version v3.4.0 ### Feature type New functionality ### Proposed functionality Allow racking an existing device from the rack view (in addition to being able to create a new device via that flow). This can easily be achieved when modelling after the "Assign existing IP address to interface" flow. I'll put up a PR for it shortly. ### Use case This makes it a lot easier to rack existing devices when doing rack work. ### Database changes n/a ### External dependencies n/a
adam added the type: featurepending closurestatus: under review labels 2025-12-29 20:22:34 +01:00
adam closed this issue 2025-12-29 20:22:34 +01:00
adam commented 2025-12-29 20:22:35 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Dec 16, 2022):

This functionality was originally proposed in #1830, though it was determined at the time that the development effort required would not be worthwhile.

This can easily be achieved when modelling after the "Assign existing IP address to interface" flow.

This workflow unfortunately is a snowflake, and needs to be rearchitected to function in a scalable manner. We want to avoid replicating it prior to that because it would only generate additional future work. (FYI this is why we ask contributors to wait for an FR to be accepted before beginning work on a PR.)

@jeremystretch commented on GitHub (Dec 16, 2022): This functionality was originally proposed in #1830, though it was determined at the time that the development effort required would not be worthwhile. > This can easily be achieved when modelling after the "Assign existing IP address to interface" flow. This workflow unfortunately is a snowflake, and needs to be rearchitected to function in a scalable manner. We want to avoid replicating it prior to that because it would only generate additional future work. (FYI this is why we ask contributors to wait for an FR to be accepted before beginning work on a PR.)
adam commented 2025-12-29 20:22:35 +01:00
Author
Owner
Copy Link

@fabi125 commented on GitHub (Dec 16, 2022):

I saw the comment in #1830, which is also why I added a PR to this, to show that the development effort (at least when duplicating the assign ip workflow) is minimal.

Do you have any pointers how that workflow could be rearchitected so we can add this?

@fabi125 commented on GitHub (Dec 16, 2022): I saw the comment in #1830, which is also why I added a PR to this, to show that the development effort (at least when duplicating the assign ip workflow) is minimal. Do you have any pointers how that workflow could be rearchitected so we can add this?
adam commented 2025-12-29 20:22:35 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Feb 15, 2023):

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 15, 2023): 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:22:36 +01:00
Author
Owner
Copy Link

@fabi125 commented on GitHub (Feb 15, 2023):

It looks like there has been repeated requests for this feature. We are happy to contribute code here if someone could give us some pointers on how you would like this workflow for this and "assign existing ip to interface" to look like.

@fabi125 commented on GitHub (Feb 15, 2023): It looks like there has been repeated requests for this feature. We are happy to contribute code here if someone could give us some pointers on how you would like this workflow for this and "assign existing ip to interface" to look like.
adam commented 2025-12-29 20:22:36 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Mar 17, 2023):

Closing this for inactivity. @fabi125 I encourage you to explore how we're leveraging HTMX in recent NetBox releases, which may provide some guidance for devising a feasible workflow. Happy to re-open this if you can come up with something.

@jeremystretch commented on GitHub (Mar 17, 2023): Closing this for inactivity. @fabi125 I encourage you to explore how we're leveraging HTMX in recent NetBox releases, which may provide some guidance for devising a feasible workflow. Happy to re-open this if you can come up with something.
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 pending closure status: under review 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#7372
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?