Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Version 0.14.0 fails with config scan #282

Closed
tw-sarah opened this issue Nov 9, 2023 · 1 comment
Closed

Version 0.14.0 fails with config scan #282

tw-sarah opened this issue Nov 9, 2023 · 1 comment

Comments

@tw-sarah
Copy link

tw-sarah commented Nov 9, 2023

We are using the Trivy action in our pipeline for scan-type of image and config.
We have been using aquasecurity/trivy-action@master and it was working fine until Nov 7.
Now, the config scan-type fails if we run with master or 0.14.0. It only runs correctly if we downgrade version 0.13.1.
(The image scan type works fine with both versions)

There are not any actual violations reported, and I can run the Trivy command on our config locally and it passes (latest version of Trivy 0.47.0). The github action turns red after a few seconds with no error reason reported. This happens in all of our Github repos.

We are running with this config:

      - name: Run Trivy scan on config
        uses: aquasecurity/[email protected]
        with:
          scan-type: 'config'
          hide-progress: false
          format: 'sarif'
          output: 'trivy-results.sarif'
          exit-code: '1'
          ignore-unfixed: true
          severity: 'CRITICAL,HIGH'
          skip-dirs: 'node_modules'
@tw-sarah tw-sarah closed this as completed Nov 9, 2023
@tw-sarah
Copy link
Author

tw-sarah commented Nov 9, 2023

Closing this issue because I found the same reported in #281 that already posts a solution.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant