(Fix #883) Additionally expose ipv4/6 cidrs in github_ip_ranges data source #884
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.
Fixes #883
https://api.github.com/meta recently changed and now includes both ipv4 and ipv6 cidrs
When integrating the
github_ip_ranges
data source with resources from other providers requiring cidrs to be specified separately (ipv4
andipv6
), you find yourself writing additional terraform logic to split them.ref. https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/security_group_rule#ipv6_cidr_blocks
This pull request encapsulates the logic in the
github_ip_ranges
data source, by including additional_ipv4
and_ipv6
outputs - it maintains backwards compatibility intact as it preserves the original data source outputs too.