-
Notifications
You must be signed in to change notification settings - Fork 101
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
bump to image version 3.2.4 is causing failures #162
Comments
Hi @igitcode, are you using a Bridgecrew API Key or is this without any API key? |
No API key. Have now seen this same issue across 2 customer environments. For now we've change from using |
Hi @igitcode , any special configuration, environment variables, flags we should consider for the investigation? Currently we fail to reproduce it 🙏 |
I am getting exactly the same error while scanning my helm chart. Action invocation is quite simple:
|
My config looks like this. We are passing in different
both projects are using GitHub hosted runners. Not sure if this would make any difference. |
Thank you. We will prioritize it internally. If you are Prisma Cloud customers, feel free to contact your Customer Success representatives to increase the priority of this issue. |
I can confirm, that switching the action to this version makes it work again. |
Experiencing same using below GH Action step. Curious part of the error seems to be url resolution:
GH Action Step:
runtime checkov-action
|
I feel that some may not notice it's happening as is doesn't cause the GH workflow to fail |
so if it is the transition from 3.2.3(Jan 31) to 3.2.4(Feb1) perhaps this issue should be attached to the checkov repo, specifically this commit I searched the checkov-action and checkov repo's for 'v2/guidelines' and the only file I came back with was
In the above commit, on line 116, removed from the definition value "self.bc_api_url" was the default 'https://www.bridgecrew.cloud'. So it is now only populated if the OS has BC_API_URL set. It seems the idea was to have this value blank so that on line 203 "def setup_api_urls(self) -> None:" would automagically set "api_url" to 'https://api0.prismacloud.io' however, somewhere in logic it appears "bc_api_url" is being set to the string "None" |
In a third customer environment the same issue was reported, on latest version |
Thanks, folks. We will investigate the issue and get this resolved. |
@igitcode |
@omryMen Still seeing the issue on |
@igitcode can you add the new log you're seeing |
@igitcode |
confirmed this is no longer happening as of |
We are facing this issue when using a custom SSL certificate. Is there a way to pass the custom SSL cert or ignore warning?
|
@askkhan84 The issue is you have a You can pass a custom CA certificate that signs the certificate (I had a similar issue while using vpn and needed to pass my organization CA cert). |
All our pipelines started throwing this error this morning, which have all been after the bump to image version 3.2.4
The text was updated successfully, but these errors were encountered: