Set Accepted status for running Vulnerability Exports
What does this MR do?
Related to #197494 (closed)
This MR improves API for Vulnerability Exports (/api/v4/projects/:project_id/vulnerability_exports/:export_id) to return 202 Accepted HTTP code when export is not yet finished/failed. This is especially important for https://gitlab.com/gitlab-org/gitlab/-/blob/master/app/assets/javascripts/lib/utils/poll_until_complete.js#L33, because when code is 200 OK, the callback is resolved, which leads to try downloading incompleted report.
Does this MR meet the acceptance criteria?
Conformity
-
Changelog entry -
Documentation (if required) -
Code review guidelines -
Merge request performance guidelines -
Style guides -
Database guides -
Separation of EE specific content
Availability and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. - [-] Tested in all supported browsers
- [-] Informed Infrastructure department of a default or new setting change, if applicable per definition of done
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
- [-] Label as security and @ mention
@gitlab-com/gl-security/appsec - [-] The MR includes necessary changes to maintain consistency between UI, API, email, or other methods
- [-] Security reports checked/validated by a reviewer from the AppSec team