-
Notifications
You must be signed in to change notification settings - Fork 67
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
fix: Check standard logs in AwsSolutions-CFR3 #1877
Draft
georeeve
wants to merge
6
commits into
cdklabs:main
Choose a base branch
from
georeeve:cf-standard-v2
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
Changes from 1 commit
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
0e4648c
fix: Check standard logs in AwsSolutions-CFR3
georeeve 259dcbf
Set in a map to check later
georeeve 42ef106
Traverse Stack to find matching CfnDeliverySource
georeeve 25dd43b
Add Noncompliance test to check multiple distributions
georeeve a73f1bb
Also check CfnDelivery
georeeve bb16f40
Try to resolve SSM parameters
georeeve File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Next
Next commit
fix: Check standard logs in AwsSolutions-CFR3
- Loading branch information
commit 0e4648ce5dd0f47bd91e3e52e0bd49af57f73925
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@dontirun I'm wondering if you know of a way to check this? I've tried to use
Template.fromStack(Stack.of(node))
and then find the resources that way, but that seems to really slow the tests down. Is there a simpler solution that I'm missing?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think there might actually be a better solution here. Can we mark all of the
CfnDistribution
's asNOT_APPLICABLE
, add them to a Map and then at the end of the Stack we evaluate and retrospectively mark them asCOMPLIANT
orNOT_COMPLIANT
dependent on whether we've seen aCfnDeliverySource
for them? Is there a method of doing that?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Or maybe we just traverse the entire Stack when we see a
CfnDistribution
to check if anyCfnDeliverySource
's are present, similar to what we do in WAFv2LoggingEnabled.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've just pushed a commit to match the WAF rule, let me know if you think that's the right solution.