-
getRemediation query has problem with filter - image and vulnerability mixed up.
It seems there is a bug where the filter only works when the values for vulnerabiltiy and images are passed other way arround.
-
Sorting by expirationDate
expirationDate filter (ascending or by nearest expirity first) has to be supported for queries of getRemediation
3 deleteRemediation - correct input to delete one remediation
delete one of remediations returned from the list get by getRemediation with filters. When deleteRemediation is called (by mutation) with id it does not work.
It is unknown what is correct input to delete a single remediation (e.g. do we need to pass image, service, or other fields in addition to id).
Task Description
A clear and concise description of what the task entails.
Acceptance Criteria:
Expected Test:
Add any information about how this will be tested.
getRemediation query has problem with filter - image and vulnerability mixed up.
It seems there is a bug where the filter only works when the values for vulnerabiltiy and images are passed other way arround.
Sorting by expirationDate
expirationDate filter (ascending or by nearest expirity first) has to be supported for queries of getRemediation
3 deleteRemediation - correct input to delete one remediation
delete one of remediations returned from the list get by getRemediation with filters. When deleteRemediation is called (by mutation) with id it does not work.
It is unknown what is correct input to delete a single remediation (e.g. do we need to pass image, service, or other fields in addition to id).
Task Description
A clear and concise description of what the task entails.
Acceptance Criteria:
Expected Test:
Add any information about how this will be tested.