Remove `cluster_image_scanning` from Scan execution rule mode dropdown
Summary
cluster_image_scanning
does the same thing as container_scanning
and we want to consolidate naming
Steps to reproduce
- Upload a GitLab Ultimate license
- Navigate to a project => Security & Compliance => Policies => New policy => Scan Execution policy
- Select a scan type
Example Project
What is the current bug behavior?
A user can select cluster_image_scanning
What is the expected correct behavior?
A user cannot select cluster_image_scanning
Relevant logs and/or screenshots
Possible fixes
-
frontend remove cluster_image_scanning
from constants.js -
frontend if a user puts in cluster_image_scanning
into yaml, disable rule mode
Edited by Alexander Turinske