-
Notifications
You must be signed in to change notification settings - Fork 290
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
Stop checkov "300" error through code #5133
Comments
This doesn't need to be fixed does it? It looks like a known issue in Checkov: bridgecrewio/checkov#5363 You can see it being handled in code like so:
|
That being the case I'd say this just needs a skip statement. Maybe with a comment to review it later. |
Replaced the comment (fits on one line on my resolution) with this and noted the above URL below #checkov:skip=CKV_AWS_300: "Ensure S3 lifecycle configuration sets period for aborting failed uploads - There is a known checkov error needs to be checked for resolution" Added quotes around the second comment in here to prevent the URL listing the site |
Did not make the above changes as the current fix requirement cannot be satisfied. We should maybe review this when a fix is implemented on checkov for this feature. |
Moved into backlog |
Looks like this has now been resolved, so we can remove the 'skip' |
Agreed @SimonPPledger - I've checked the Chekov issue and it's resolved, so any future failures may be legit. I'll close this issue. |
Expected Behavior
At present we have the following in place on the modernisation-platform-terraform-s3-bucket in two places #checkov:skip=CKV_AWS_300: "Ensure S3 lifecycle configuration sets period for aborting failed uploads"
We want to add the code to remove this skip
Actual Behavior
At present an error for the top section
"Check: CKV_AWS_300: “Ensure S3 lifecycle configuration sets period for aborting failed uploads”
FAILED for resource: aws_s3_bucket_lifecycle_configuration.default
File: /main.tf:49-113"
appears. A similar one appears for the lower section.
With the skip in place this stops the check being undertaken and the error does not appear.
There is code in place on the "top" section (line 67 -76) but it does not appear to work currently. This needs to be fixed or replaced.
Steps to Reproduce the Problem
To reproduce the error the skips would need to be reviewed and a PR raised. It's not advisable to do this!
Version
No response
Modules
No response
Account
No response
The text was updated successfully, but these errors were encountered: