-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
CKV2_GCP_10 - false positive #4812
Comments
In your case you can't specify trigger_http as the attributes are not compatible with an event trigger block, and so you should be specifying https_trigger_security_level on which the check is based. |
If the Cloud Function is not HTTP trigger we should use https_trigger_security_level anyway ? is that you are saying? |
Thanks for contributing to Checkov! We've automatically marked this issue as stale to keep our issues list tidy, because it has not had any activity for 6 months. It will be closed in 14 days if no further activity occurs. Commenting on this issue will remove the stale tag. If you want to talk through the issue or help us understand the priority and context, feel free to add a comment or join us in the Checkov slack channel at https://slack.bridgecrew.io |
Closing issue due to inactivity. If you feel this is in error, please re-open, or reach out to the community via slack: https://slack.bridgecrew.io Thanks! |
Description
CKV2_GCP_10 - Ensure GCP Cloud Function HTTP trigger is secured
This should only alert if the cloud function is HTTP triggered.
You should check the trigger type to see if is HTTP or not(
trigger_http = true
), example bellow of a not HTTP triggered function.Examples
Version :
The text was updated successfully, but these errors were encountered: