Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add "has_virtual_device_context" filter to device filters in UI and API #14948

Closed
SaschaSchwarzK opened this issue Jan 26, 2024 · 1 comment · Fixed by #16209
Closed

Add "has_virtual_device_context" filter to device filters in UI and API #14948

SaschaSchwarzK opened this issue Jan 26, 2024 · 1 comment · Fixed by #16209
Assignees
Labels
status: accepted This issue has been accepted for implementation type: feature Introduction of new functionality to the application

Comments

@SaschaSchwarzK
Copy link

NetBox version

v3.7.1

Feature type

Change to existing functionality

Proposed functionality

The only way to find devices that have virtual device context is to get all virtual-device-contexts and extract the list of related devices from that. Similar to the has_primary_ip filter.

Use case

Get the list of devices with have or have not a virtual-device-context with a simple boolean filter.

Database changes

Not required

External dependencies

None

@SaschaSchwarzK SaschaSchwarzK added the type: feature Introduction of new functionality to the application label Jan 26, 2024
@jeremystretch jeremystretch added the status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation label Mar 9, 2024
@jeremystretch
Copy link
Member

There's ongoing work under #15237 to identify and test for missing filters. It hasn't yet expanded to checking reverse ForeignKey relationships but should eventually cover this sort of thing.

@arthanson arthanson self-assigned this May 20, 2024
@arthanson arthanson removed the status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation label May 20, 2024
@jeremystretch jeremystretch added the status: accepted This issue has been accepted for implementation label May 21, 2024
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 21, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
status: accepted This issue has been accepted for implementation type: feature Introduction of new functionality to the application
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants