-
Notifications
You must be signed in to change notification settings - Fork 782
Closed as not planned
Labels
stale~backendBackend-related issue.Backend-related issue.~engineering-initiatedEngineering-initiated story, such as a bug, refactor, or contributor experience improvement.Engineering-initiated story, such as a bug, refactor, or contributor experience improvement.~legacy-interface-product-groupAssociated with the legacy "interface" product group. (No longer exists)Associated with the legacy "interface" product group. (No longer exists)
Description
Goal
- In an ideal world, the host API will return an error message if one of the filters is invalid (e.g. policy_id=23948023 is invalid, mdm_id=21304983450 is invalid).
- Currently this is happening for the software_id being invalid(see screenshot), but not other filters.
- Other filters that are not erroring out just respond with an empty host array
hosts: [] - We would want to have a similar error response to the software_id being invalid applied to other invalid filters
This is related to #7209 and potentially creating a similar banner for any invalid filter. It's just hard to build if the validation process is not consistent.
TODO
How?
- Apply to the following filters:
mdm_idpolicy_idmunki_issuesos_nameos_version
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
stale~backendBackend-related issue.Backend-related issue.~engineering-initiatedEngineering-initiated story, such as a bug, refactor, or contributor experience improvement.Engineering-initiated story, such as a bug, refactor, or contributor experience improvement.~legacy-interface-product-groupAssociated with the legacy "interface" product group. (No longer exists)Associated with the legacy "interface" product group. (No longer exists)
