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

Add query parameters to dcim/module API #6496

New Issue
Closed
opened 2025-12-29 19:41:34 +01:00 by adam · 1 comment
adam commented 2025-12-29 19:41:34 +01:00
Owner
Copy Link

Originally created by @mdoerr2s on GitHub (May 19, 2022).

NetBox version

v3.2.3

Feature type

Change to existing functionality

Proposed functionality

As discussed in #9393, the REST API for modules (dcim/module) lacks the functionality to query for modules in a specific module_bay. Also the API endpoint for module_bay, does not provide an argument for installed_device, making it hard to query for modules, located in a specific module_bay.

Since the data model already provides the information, only additional parameters for the API need to be introduced.

Use case

Enable users to query for modules, located in a specific module_bay of interest. Increasing usability of API by enabling returning unique responses, without having to query devices and getting a list, where this information needs to be extracted from.

Database changes

No, since the data model of module already has all information needed, as can be explored via nbshell.

External dependencies

None

Originally created by @mdoerr2s on GitHub (May 19, 2022). ### NetBox version v3.2.3 ### Feature type Change to existing functionality ### Proposed functionality As discussed in [#9393](https://github.com/netbox-community/netbox/discussions/9393), the REST API for modules (dcim/module) lacks the functionality to query for modules in a specific module_bay. Also the API endpoint for module_bay, does not provide an argument for installed_device, making it hard to query for modules, located in a specific module_bay. Since the data model already provides the information, only additional parameters for the API need to be introduced. ### Use case Enable users to query for modules, located in a specific module_bay of interest. Increasing usability of API by enabling returning unique responses, without having to query devices and getting a list, where this information needs to be extracted from. ### Database changes No, since the data model of module already has all information needed, as can be explored via nbshell. ### External dependencies None
adam added the status: acceptedtype: feature labels 2025-12-29 19:41:34 +01:00
adam closed this issue 2025-12-29 19:41:34 +01:00
adam commented 2025-12-29 19:41:34 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jun 23, 2022):

Also the API endpoint for module_bay, does not provide an argument for installed_device, making it hard to query for modules, located in a specific module_bay.

This needs a separate issue; I've opened bug report #9597 for this.

@jeremystretch commented on GitHub (Jun 23, 2022): > Also the API endpoint for module_bay, does not provide an argument for installed_device, making it hard to query for modules, located in a specific module_bay. This needs a separate issue; I've opened bug report #9597 for this.
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: 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#6496
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?