-
Notifications
You must be signed in to change notification settings - Fork 142
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
Adding WAF Rule Exclusions to WAF Configuration resource #328
Conversation
During this implementation, I've refactored some of the WAF acceptance tests to reduce overlapping: 1. TestAccFastlyServiceWAFVersionV1ImportWithRules was merged into TestAccFastlyServiceWAFVersionV1Import. This tests was also enhanced to include WAF exclusions 1. TestAccFastlyServiceWAFVersionV1AddWithRules and TestAccFastlyServiceWAFVersionV1DeleteRules was merged into TestAccFastlyServiceWAFVersionV1UpdateRules. The update tests was performing add, update and delete already. TestAccFastlyServiceWAFVersionV1UpdateRules was renamed to TestAccFastlyServiceWAFVersionV1AddUpdateDeleteRules to make it clearer Co-authored-by: Zsolt Balvanyos <[email protected]>
PR updated to use WAF Rule exclusion terminology Here's the new acc test results Acceptance Test Results
|
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.
Looking good, a couple of small nits.
resp, e := conn.ListAllWAFRuleExclusions(&gofastly.ListAllWAFRuleExclusionsInput{ | ||
WAFID: wafID, | ||
WAFVersionNumber: wafVersionNumber, | ||
Include: strToPtr("waf_rules"), |
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.
This may need to change to a slice, pending discussion on the go-fastly PR.
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.
Updated
…-fastly to v2.0.0-alpha.2. Changing provider to use new struct format (include is now a slice instead of a string). Cleaned up go.sum
Acc Test results for the WAF. Acceptance Test Results
|
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.
👍 LGTM
During this implementation, I've refactored some of the WAF acceptance tests to reduce overlapping:
TestAccFastlyServiceWAFVersionV1ImportWithRules
was merged intoTestAccFastlyServiceWAFVersionV1Import
. This tests was also enhanced to include WAF exclusions.TestAccFastlyServiceWAFVersionV1AddWithRules
andTestAccFastlyServiceWAFVersionV1DeleteRules
was merged intoTestAccFastlyServiceWAFVersionV1UpdateRules
. The update tests was performing add, update and delete already.TestAccFastlyServiceWAFVersionV1UpdateRules
was renamed toTestAccFastlyServiceWAFVersionV1AddUpdateDeleteRules
to make it clearerPS: When fastly/go-fastly#223 is approved and merged, I'll need just update the
go.mod
and vendor folder with the latest tag.Acceptance Test Results