Allow Runner Tags to be Setup for On Demand DAST

Release notes

Problem to solve

As a user of On Demand DAST, I want to run DAST on a site that only a subset of my GitLab Runners have access to, which requires me to reference a runner tag to setup On Demand DAST or it removes the ability to have a set of different types of runners.

User experience goal

During the setup of On Demand DAST, users could specify a Runner Tag to be referenced so that DAST scans use specific runners rather than generic runners (including the GitLab Runner Cloud on SaaS) while also allowing the project to still use generic runners for all other jobs on the given project.

Proposal

Add the ability to set a runner tag (or tags) when configuring On Demand DAST.

Links / references

This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.

Possible Workaround

• Setup DAST via GitLab CI and have it run on a scheduled pipeline only, and specify the Runner Tags on that job.