-
Notifications
You must be signed in to change notification settings - Fork 23
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
4.3.0 #346
Merged
Merged
4.3.0 #346
Conversation
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
I've found issues running it on Node 20. Also adds a change to ensure that only npm is used for managing dependencies, done by the script `npx only-allow npm`. Not a good idea to mix dependency managers on the same project, like npm and Yarn.
This commit differentiate ipsets from different FMS configs by adding the name of the webacl to it. Without this commit, trying to run aws-firewall-factory for two configs which uses a ipset with the same name would give a error on CloudFormation ('IpSet with name x already exists')
This commit helps a lot by immediately letting us know which rule failed capacity checking and requires fixes
The prop ScopeDownStatement of RateBasedStatements can have And, Or and Not statements, just like any other Statement. Without this fix, deploying RateBasedStatements with complex ScopeDownStatement fails on capacity checking.
The ManagedServiceData has a hard limit of 8192 characters. I've asked AWS about raising it and they said that this is a hard limit and they can't raise it. This commit is for saving as much chars as we can out of the ManagedServiceData prop, for squeezing in our rules (even if they have a ton of RuleActionOverrides on them)
This adds a dynamic import of the firewall config for enabling people that want to run async code on then, ensuring that all async code will run during the import
Sometimes the lambda that fetches the latest version of the ManagedRules fetches a 'beta' version, one that shouldn't be used on WAF. Without this fix the error below can happen on CloudFormation: ``` Resource handler returned message: The managed rule group AWSManagedRulesLinuxRuleSet's version [Version_2.2_PLUS_RC_COUNT] isn't valid. This managed rule group version must be an available version for the WAF managed rule group, and have the same format. ```
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Added
Fixed
EnforceUpdate
tofalse
.