Remove trivy from trigger-scanner-update job
What does this MR do?
Updating trivy to a more recent version is currently blocked by Add workaround in Container Scanning to allow u... (gitlab-org/gitlab#404587 - closed), however, a scheduled pipeline keeps creating MRs to update trivy to the most recent version, for example: Update trivy to version 0.43.1 (!2909 - closed).
These version bump MRs for trivy cannot be merged until Add workaround in Container Scanning to allow u... (gitlab-org/gitlab#404587 - closed) has been completed, so we should avoid creating them in the first place, which what this MR does.
What are the relevant issue numbers?
Add workaround in Container Scanning to allow u... (gitlab-org/gitlab#404587 - closed)
Does this MR meet the acceptance criteria?
- [-] Changelog trailer added
-
Documentation created/updated for GitLab EE, if necessary -
Documentation created/updated for this project, if necessary -
Documentation reviewed by technical writer or follow-up review issue created -
Tests added for this feature/bug -
Job definition updated, if necessary -
Conforms to the code review guidelines -
Conforms to the Go guidelines -
Security reports checked/validated by reviewer