Add forgotten dependencies rejection to the job definition in DAST vendored template
Problem to solve
This was missed during the release of vendored templates (all other templates have this in their job definitions).
dependencies: directive to the DAST vendored template in the next upcoming release.
GIT_STRATEGY: falsedirective to the DAST vendored template in the next upcoming release.
- Update for DAST examples documentation (manual job definition)
What does success look like, and how can we measure that?
Customers don't have problems with unwanted artifacts uploading when using the DAST job definition, either from vendored template or manually.
What is the type of buyer?
GitLab Ultimate users