Peter Benjamin

I was able to work around this issue in my workflow by specifying the platform in `trivy.yaml` file. Example: 1. In `trivy.yaml`: ```yaml image: platform: linux/arm64 ``` 2. In GitHub...

Agreed. I would like to see an input for platform, like: ```yaml - name: Run Trivy vulnerability scanner for distroless container uses: aquasecurity/[email protected] with: image-ref: 'ghcr.io/someimage:${{github.sha}}-distroless' platform: 'linux/arm64' format: 'sarif'...

I just came across [this bit](https://github.com/aquasecurity/trivy-action?tab=readme-ov-file#environment-variables) of documentation in the action's README: > You can use [Trivy environment variables](https://aquasecurity.github.io/trivy/latest/docs/configuration/#environment-variables) to set the necessary options (including flags that are not supported...

A similar question was asked on `tpope/vim-fugitive` here: https://github.com/tpope/vim-fugitive/issues/2249#issuecomment-1874566335 **TL;DR** ``` :Git -c pager.diff=delta diff ```