fix: trivy execution

.gitlab-ci.yml

@@ -67,23 +67,7 @@ dev_trivy:
     - trivy --version
     # cache cleanup is needed when scanning images with the same tags, it does not remove the database
     - time trivy image --clear-cache
-    # update vulnerabilities db
-    # - time trivy --download-db-only --no-progress --cache-dir .trivycache/
-    # Builds report and puts it in the default workdir $CI_PROJECT_DIR, so `artifacts:` can take it from there
-    - time trivy --exit-code 0 --cache-dir .trivycache/ --no-progress --format template --template "@/contrib/gitlab.tpl"
-        --output "$CI_PROJECT_DIR/gl-container-scanning-report.json" image "$FULL_IMAGE_NAME"
-    # Prints full report
-    - time trivy --exit-code 0 --cache-dir .trivycache/ --no-progress image "$FULL_IMAGE_NAME"
-    # Fail on critical vulnerabilities
-    - time trivy --exit-code 1 --cache-dir .trivycache/ --severity CRITICAL --no-progress image "$FULL_IMAGE_NAME"
-  cache:
-    paths:
-      - .trivycache/
-  # Enables https://docs.gitlab.com/ee/user/application_security/container_scanning/ (Container Scanning report is available on GitLab EE Ultimate or GitLab.com Gold)
-  artifacts:
-    when: always
-    reports:
-      container_scanning: gl-container-scanning-report.json
+    - trivy image --clear-cache $IMAGE_TAG
   only:
     - master