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
When running on a self hosted GitHub Enterprise Server (GHES) the new version of setup-trivy is failing because it's using the checkout action without allowing the token and github-server-url to be overridden. In that case it tries to check out contrib/install.sh from aquasecurity/trivy on the local GHES instead of from https://github.com/aquasecurity/trivy.
Updating setup-trivy (and the trivy-action) with optional parameters for token and github-server-url and passing those to actions/checkout would probably make it compatible with GHES as well (although more config would be needed for users of the action on GHES).
The text was updated successfully, but these errors were encountered:
Since recently, we have a similar problem on our GHES, also with the checkout step. In our case, the default branch cannot be determined by the checkout action, I believe because it is operating on github.com URLs.
Can you test these changes with GHES?
use commit from my fork (uses: DmitriyLewen/setup-trivy@108c12b3f1803ed4e0e9780fb857f6b00946cb56)
with optional parameters for token and github-server-url
trivy is a public repository. I hope rewriting token doesn't break action/checkout.
We probably don't need to add input for github-server-url, since in all cases action/checkout in setup-trivy should connect to the github.com server.
we will explicitly indicate this server and that will be enough
Hi.
When running on a self hosted GitHub Enterprise Server (GHES) the new version of
setup-trivy
is failing because it's using the checkout action without allowing thetoken
andgithub-server-url
to be overridden. In that case it tries to check outcontrib/install.sh
fromaquasecurity/trivy
on the local GHES instead of from https://github.com/aquasecurity/trivy.Updating
setup-trivy
(and thetrivy-action
) with optional parameters fortoken
andgithub-server-url
and passing those toactions/checkout
would probably make it compatible with GHES as well (although more config would be needed for users of the action on GHES).The text was updated successfully, but these errors were encountered: