Replace container_scanning job definition with a vendored template
Problem to solve
Job definition for container scanning is frozen, and can't be easily updated without creating breaking changes.
With gitlab-ce#53445 (closed), we'll be able to ship a template embedded with each version of GitLab. The template can be updated from one version to another, without impacting our users.
What does success look like, and how can we measure that?
The new official job definition is a single inclusion instruction:
include: template: Container-Scanning.gitlab-ci.yml
Links / references
Container-Scanning.gitlab-ci.ymlwith the contents from the example to the templates dir under
- Test in the development environment on a test project
- Update the Documentation for the Container Scanning CI configuration