Skip to content

Don't propagate the parse errors to the client for `vulnerability_findings` endpoint

Mehmet Emin INAC requested to merge do_not_propagate_the_parse_error_to_callers into master

What does this MR do and why?

It is expected to receive a malformed report artifact so there is no point to raise parsing errors back to the user from the REST APIs.

This MR introduces a change to capture parsing errors and respond with an empty response body if parsing error happans.

Related to #342973 (closed).

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Edited by Mehmet Emin INAC

Merge request reports