Simple idea for centralizing the control of the vulnerability-allowlist.yml configuration file
In this post, I’ll share a specific situation I had some time ago and how I went about solving it. It’s a rather niche case, but it may be of interest to those who deal with similar challenges and:
- use GitLab
- use
Container-Scanning.gitlab-ci.yml
GitLab template - want to manage
vulnerability-allowlist.yml
from a single location - …or simply curious what it’s all about