You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be great if checkov provided a problem matcher with this action so end users could receive a richer error output experience in GitHub Actions by allowing test failures and their reasoning to bubble up to the UI as detected by the problem matcher https://github.com/jsoref/actions-runner/blob/main/docs/adrs/0276-problem-matchers.md.
This would be especially nice as it's common to upload your checkov output to something else like Datadog. To do this you would want checkov to output in something machine friendly like XML. To then get nice output for humans in the pipeline you currently would need to run checkov a second time with something human friendly as the output. This second run could be avoided by having a problem matcher bubble the errors up to the GitHub UI meaning checkov only needs to be ran once.
It would be great if checkov provided a problem matcher with this action so end users could receive a richer error output experience in GitHub Actions by allowing test failures and their reasoning to bubble up to the UI as detected by the problem matcher https://github.com/jsoref/actions-runner/blob/main/docs/adrs/0276-problem-matchers.md.
This would be especially nice as it's common to upload your checkov output to something else like Datadog. To do this you would want checkov to output in something machine friendly like XML. To then get nice output for humans in the pipeline you currently would need to run checkov a second time with something human friendly as the output. This second run could be avoided by having a problem matcher bubble the errors up to the GitHub UI meaning checkov only needs to be ran once.
Here is an example of a project that provides a problem matcher https://github.com/rhysd/actionlint/blob/main/.github/actionlint-matcher.json
The text was updated successfully, but these errors were encountered: