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

Unable to store output in "table" format #238

Open
Jiri-Stary opened this issue Aug 15, 2023 · 2 comments · May be fixed by #346
Open

Unable to store output in "table" format #238

Jiri-Stary opened this issue Aug 15, 2023 · 2 comments · May be fixed by #346
Assignees
Labels
enhancement New feature or request

Comments

@Jiri-Stary
Copy link

Currently there is no way to store output in table format.

I am running few different scanners in my workflow an would like to control when i show the output to the user.
Currently there is no way how to store the output to a text file in table format.

@popey popey added the enhancement New feature or request label Jul 1, 2024
@kzantow
Copy link
Contributor

kzantow commented Sep 18, 2024

Hi @Jiri-Stary -- sorry for the delay here; you're right, today if you use the table output format, this defaults to output to the log instead of a file, however there is a workaround if you really want this output to a file, you can use the GRYPE_FILE environment variable, e.g.:

      - uses: anchore/scan-action@main
        id: scan-table-to-file
        with:
          image: alpine:3.15
          fail-build: false
          severity-cutoff: medium
          output-format: table
        env:
          GRYPE_FILE: table.out

Example run here: https://github.com/kzantow-anchore/scan-action-test/actions/runs/10924951451/job/30325259711#step:5:9

@kzantow kzantow moved this to Stalled in OSS Sep 18, 2024
@kzantow kzantow moved this from Stalled to Backlog in OSS Sep 18, 2024
@kzantow
Copy link
Contributor

kzantow commented Sep 18, 2024

Developer note: we may want to support multiple outputs and/or template output, which also could help improve this experience, but we probably won't change the default behavior here; also, adding an output-file property explicitly should cause table output to a file instead of the console.

@willmurphyscode willmurphyscode moved this from Backlog to In Review in OSS Oct 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: In Review
Development

Successfully merging a pull request may close this issue.

3 participants