Auto DevOps DAST job shouldn’t be added to the pipeline if dast_environment_deploy job is skipped
Summary
With auto DevOps, if there is no available Kubernetes cluster, DAST job is running (and failing) even if dast_environment_deploy is skipped.
Steps to reproduce
- Go to a new project
- Enable Auto DevOps
- Push some code
- Observe pipeline
What is the current bug behavior?
DAST job is added to pipeline
What is the expected correct behavior?
DAST job is skipped