We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
output-file
This is a "nice-to-have" feature request.
Currently the output file name is hardcoded to ./results.json or results.sarif. See here
./results.json
results.sarif
I would like some control over the file name, currently i need to add an extra step like so
- name: Run grype vulnerability scanner uses: anchore/scan-action@v3 id: grype-scan with: path: . fail-build: false output-format: sarif - name: Output report to custom file run: cat ${{ steps.grype-scan.outputs.sarif }} > grype-results.sarif - name: Upload vulnerability report uses: actions/upload-artifact@master if: always() with: name: grype-results path: | grype-results.sarif if-no-files-found: warn
This avoids automatic name clashes with results.json produced by other steps in the same job.
results.json
Note: This parameter is supported by "trivy". See here
PS: I'd be happy to send a PR if you guys agree.
The text was updated successfully, but these errors were encountered:
Hi @sidmitra, we would be happy to review a PR for this! Let us know if we can help, and thanks.
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
This is a "nice-to-have" feature request.
Currently the output file name is hardcoded to
./results.json
orresults.sarif
. See hereI would like some control over the file name, currently i need to add an extra step like so
This avoids automatic name clashes with
results.json
produced by other steps in the same job.Note: This parameter is supported by "trivy". See here
PS: I'd be happy to send a PR if you guys agree.
The text was updated successfully, but these errors were encountered: