Remove DAST unsupported command line argument for progress files
What does this MR do?
Removes the unsupported -p
option that in a previous version of DAST would allow users to specify a ZAP progress file. The progress file allowed users to specify which vulnerabilities they were working on, and this would be reflected in the console output of the DAST job.
This command-line option has been broken for some time. Even when the feature was working as intended, it only affected the console output, not the DAST JSON report that is used on the Security Dashboard. For these reasons, it has been decided to keep the command-line option as a no-op function. It will be removed in release 14.0
.
What are the relevant issue numbers?
gitlab-org/gitlab#218815 (closed)
Does this MR meet the acceptance criteria?
-
Changelog entry added -
Documentation created/updated for GitLab EE, if necessary -
Documentation created/updated for this project, if necessary -
Documentation reviewed by technical writer or follow-up review issue created -
Tests added for this feature/bug -
Job definition updated, if necessary -
Job definition example -
Vendored CI Templates (also in CE)
-
-
Conforms to the code review guidelines -
Conforms to the Go guidelines -
Security reports checked/validated by reviewer
Edited by Cameron Swords