-
Notifications
You must be signed in to change notification settings - Fork 180
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
Not applicable SCA checks should be filtered by result
#5027
Closed
2 tasks done
Labels
type/bug
Bug issue
Comments
6 tasks
6 tasks
Changes
Side changes
|
This was
linked to
pull requests
Jan 6, 2023
5 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
In a recent meeting, the API , core and frontend teams agree to apply changes in how the plugin should get the checks that are not applicable.
The core team and framework team will do changes to the
result
andstatus
fields that are merged into one field. So the possible values for theresult
field can be:passed
failed
not applicable
With this change, we can use the API endpoint to get the not applicable SCA checks through the
result
query parameter in the API endpoint:This issue is related to:
result
query parameter in the API request wazuh#15695 EpicGET /sca/{agent_id}/checks/{policy_id}
to changes instatus
andresult
response fields wazuh#15738 API issueTasks:
Not applicable
filter that is added from the stat to useresult
instead of the previously applied workaround of using thestatus: not applicable
query parameter.Preconditions
1.
Steps to reproduce
Expected Result
Not applicable
stat shouldresult: not applicable
or something like that (depending on the query parameter to use)result
query parameterActual Result
We changed to use the
status
query parameter withnot applicable
value as a workaround in this pull request: #4999Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here. Here you can paste log entries too or any other useful information that may help with the issue.
The text was updated successfully, but these errors were encountered: