Filter interfaces/ports on virtualchassis_id #5459

Closed
opened 2025-12-29 19:28:18 +01:00 by adam · 2 comments
Owner

Originally created by @steffenschumacher on GitHub (Oct 1, 2021).

Originally assigned to: @rhyser9 on GitHub.

NetBox version

V2.11.3

Feature type

New functionality

Proposed functionality

For the interfaces API endpoint, it would be nice if one could filter on virtualchassis_id, beyond device_id. I imagine it would be fairly simply include, but it would need to be mutually exclusive with filtering on device_id.

Use case

Efficiency in loading virtualchassis interfaces via one api request vs per-device requests

Database changes

None

External dependencies

None

Originally created by @steffenschumacher on GitHub (Oct 1, 2021). Originally assigned to: @rhyser9 on GitHub. ### NetBox version V2.11.3 ### Feature type New functionality ### Proposed functionality For the interfaces API endpoint, it would be nice if one could filter on virtualchassis_id, beyond device_id. I imagine it would be fairly simply include, but it would need to be mutually exclusive with filtering on device_id. ### Use case Efficiency in loading virtualchassis interfaces via one api request vs per-device requests ### Database changes None ### External dependencies None
adam added the status: acceptedtype: feature labels 2025-12-29 19:28:18 +01:00
adam closed this issue 2025-12-29 19:28:18 +01:00
Author
Owner

@rhyser9 commented on GitHub (Nov 11, 2021):

"...but it would need to be mutually exclusive with filtering on device_id"
I don't see that this needs to be the case. In the same way that you could specify a region and then a site within that region, you could specify a virtual chassis and then the device within that chassis. This also could assist with narrowing down the options in the device form field

@jeremystretch I can implement this.

@rhyser9 commented on GitHub (Nov 11, 2021): _"...but it would need to be mutually exclusive with filtering on device_id"_ I don't see that this needs to be the case. In the same way that you could specify a region and then a site within that region, you could specify a virtual chassis and then the device within that chassis. This also could assist with narrowing down the options in the device form field @jeremystretch I can implement this.
Author
Owner

@steffenschumacher commented on GitHub (Nov 11, 2021):

"...but it would need to be mutually exclusive with filtering on device_id"
I don't see that this needs to be the case.

True - if it’s not custom to put in guard rails like this, that’s fine - guess users of the API are grownups😉

@steffenschumacher commented on GitHub (Nov 11, 2021): > _"...but it would need to be mutually exclusive with filtering on device_id"_ I don't see that this needs to be the case. True - if it’s not custom to put in guard rails like this, that’s fine - guess users of the API are grownups😉
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#5459