feat: Allow more than 5 CIDRs in whitelist_unauthenticated_cidr_blocks #220
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.
Description
Allow more than 5 CIDRs for the whitelist_unauthenticated_cidr_blocks field by splitting into groups of 5 (AWS's limit)
Motivation and Context
Bitbucket has 15 IPs that webhooks may come from. See: https://support.atlassian.com/organization-administration/docs/ip-addresses-and-domains-for-atlassian-cloud-products/#AtlassiancloudIPrangesanddomains-OutgoingConnections
Breaking Changes
The additional
aws_lb_listener_rule
entries will get priority+ count.index
so could collide with other listeners if the user uses those priority values.How Has This Been Tested?
I deployed this using a slightly modified github-complete from this repo, then tested upgrading to my fork and no state changes were needed. Then I added more than 5 CIDRS and confirmed correct behavior.