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

return rack group with device #4223

New Issue
Closed
opened 2025-12-29 18:33:58 +01:00 by adam · 1 comment
adam commented 2025-12-29 18:33:58 +01:00
Owner
Copy Link

Originally created by @nvitaly on GitHub (Oct 28, 2020).

Environment

  • Python version: 3.7
  • NetBox version: v2.9.7

Proposed Functionality

We have rack group (cages) and we have racks, when i retrieve list of devices from API or in UI I can only see Rack, yes I can click inside and find out Rack group but this is extra request. I might gave same name of rack or even just similarly looking names in different rack groups. which makes list hard to work with.

I am currently considering just renaming Rack so it include Cage (rack group) but it seems redundant,

I propose: return adjacent to the rack rack group with the device same way we have rack, site in it.

May be I am missing something, let me know.

Use Case

Database Changes

External Dependencies

Originally created by @nvitaly on GitHub (Oct 28, 2020). <!-- NOTE: IF YOUR ISSUE DOES NOT FOLLOW THIS TEMPLATE, IT WILL BE CLOSED. This form is only for proposing specific new features or enhancements. If you have a general idea or question, please post to our mailing list instead of opening an issue: https://groups.google.com/g/netbox-discuss NOTE: Due to an excessive backlog of feature requests, we are not currently accepting any proposals which significantly extend NetBox's feature scope. Please describe the environment in which you are running NetBox. Be sure that you are running an unmodified instance of the latest stable release before submitting a bug report. --> ### Environment * Python version: 3.7 * NetBox version: v2.9.7 <!-- Describe in detail the new functionality you are proposing. Include any specific changes to work flows, data models, or the user interface. --> ### Proposed Functionality We have rack group (cages) and we have racks, when i retrieve list of devices from API or in UI I can only see Rack, yes I can click inside and find out Rack group but this is extra request. I might gave same name of rack or even just similarly looking names in different rack groups. which makes list hard to work with. I am currently considering just renaming Rack so it include Cage (rack group) but it seems redundant, I propose: return adjacent to the rack rack group with the device same way we have rack, site in it. May be I am missing something, let me know. <!-- Convey an example use case for your proposed feature. Write from the perspective of a NetBox user who would benefit from the proposed functionality and describe how. ---> ### Use Case <!-- Note any changes to the database schema necessary to support the new feature. For example, does the proposal require adding a new model or field? (Not all new features require database changes.) ---> ### Database Changes <!-- List any new dependencies on external libraries or services that this new feature would introduce. For example, does the proposal require the installation of a new Python package? (Not all new features introduce new dependencies.) --> ### External Dependencies
adam closed this issue 2025-12-29 18:33:58 +01:00
adam commented 2025-12-29 18:33:59 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Nov 17, 2020):

The REST API is necessarily limited to returning only directly related objects in most cases. Otherwise, every request would take an inordinate amount of time to process and return far more information than is needed. The API is structured so that a consumer can make efficient requests to retrieve only the specific information needed. For example, you might make one request to retrieve a set of devices and their associated racks, and then make a second request to retrieve the rack groups for each of the racks. This is a very common pattern in REST APIs, and not specific to NetBox. Alternatively, consider using a client such as pynetbox to abstract these operations.

@jeremystretch commented on GitHub (Nov 17, 2020): The REST API is necessarily limited to returning only directly related objects in most cases. Otherwise, every request would take an inordinate amount of time to process and return far more information than is needed. The API is structured so that a consumer can make efficient requests to retrieve only the specific information needed. For example, you might make one request to retrieve a set of devices and their associated racks, and then make a second request to retrieve the rack groups for each of the racks. This is a very common pattern in REST APIs, and not specific to NetBox. Alternatively, consider using a client such as [pynetbox](https://github.com/digitalocean/pynetbox) to abstract these operations.
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
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#4223
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?