You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Expected behavior and actual behavior:
When retrieving the vulnerabilities report I expect a valid report when there are no vulnerabilities.
Currently the report is:
That is invalid in the severity field: This is an enum field. "" is not a valid value for that enum.
I suggest modifying the OpenAPI specification for by either making severity optional in the HarborVulnerabilityReport field or choose a value to report as the severity, e.g. Negligible. This issue applies to all current scanner-adapter-openapi-*.yaml files.
Steps to reproduce the problem:
In Harbor: Search for a container image without vulnerabilities. Navigate to that image, in the background the retrieval of
https://<host>/api/v2.0/projects/<project>/repositories/<container>/artifacts/<sha>/additions/vulnerabilities is performed. This results in the JSON posted above.
Versions:
harbor version: v2.11.0-70255684
The text was updated successfully, but these errors were encountered:
Expected behavior and actual behavior:
When retrieving the vulnerabilities report I expect a valid report when there are no vulnerabilities.
Currently the report is:
That is invalid in the severity field: This is an enum field. "" is not a valid value for that enum.
I suggest modifying the OpenAPI specification for by either making severity optional in the HarborVulnerabilityReport field or choose a value to report as the severity, e.g. Negligible. This issue applies to all current scanner-adapter-openapi-*.yaml files.
Steps to reproduce the problem:
In Harbor: Search for a container image without vulnerabilities. Navigate to that image, in the background the retrieval of
https://<host>/api/v2.0/projects/<project>/repositories/<container>/artifacts/<sha>/additions/vulnerabilities is performed. This results in the JSON posted above.
Versions:
The text was updated successfully, but these errors were encountered: