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

Cache the assigned site, location, and rack of device components #11425

New Issue
Closed
opened 2025-12-29 21:45:06 +01:00 by adam · 0 comments
adam commented 2025-12-29 21:45:06 +01:00
Owner
Copy Link

Originally created by @jeremystretch on GitHub (Jul 29, 2025).

Originally assigned to: @jeremystretch on GitHub.

NetBox version

v4.3.5

Feature type

New functionality

Proposed functionality

For all device components, cache the assigned site and location of the parent device. This assignment will be read-only, and updated automatically whenever the device's assignment is altered.

There is an existing pattern for how this can be handled using a receiver for the post_save signal.

Use case

Saving these assignments directly on each component will obviate the need for SQL table joins when filtering device components by parent site or location. For example, consider the following REST API query:

GET /api/dcim/interfaces/?site_id=123

This currently requires a JOIN of the dcim_interface table with the dcim_device table to query the site. Copying this relationship to the dcim_interface table allows the filter to query that table directly.

Database changes

No response

External dependencies

No response

Originally created by @jeremystretch on GitHub (Jul 29, 2025). Originally assigned to: @jeremystretch on GitHub. ### NetBox version v4.3.5 ### Feature type New functionality ### Proposed functionality For all device components, cache the assigned site and location of the parent device. This assignment will be read-only, and updated automatically whenever the device's assignment is altered. There is an [existing pattern](https://github.com/netbox-community/netbox/blob/6ca390871525c248b56f9e941bc4f1fa28b86a69/netbox/dcim/signals.py#L19) for how this can be handled using a receiver for the `post_save` signal. ### Use case Saving these assignments directly on each component will obviate the need for SQL table joins when filtering device components by parent site or location. For example, consider the following REST API query: ``` GET /api/dcim/interfaces/?site_id=123 ``` This currently requires a `JOIN` of the `dcim_interface` table with the `dcim_device` table to query the site. Copying this relationship to the `dcim_interface` table allows the filter to query that table directly. ### Database changes _No response_ ### External dependencies _No response_
adam added the status: acceptedtype: featurecomplexity: medium labels 2025-12-29 21:45:06 +01:00
adam closed this issue 2025-12-29 21:45:06 +01:00
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 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#11425
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?