Terraform Aws Vpc Peering Versions Save

what

Support AWS Provider V5 Linter fixes

why

Maintenance

references

https://github.com/hashicorp/terraform-provider-aws/releases/tag/v5.0.0

Rebuild github dir from the template

what

• This PR will introduce logic to ignore certain CIDR ranges from either the requestor or acceptor VPC(s), without affecting the existing functionality.

why

• We add the CIDR range 100.64.0.0/16 to each of our EKS cluster VPCs to increase the maximum amount of assignable IP addresses when using the AWS VPC CNI.
• This causes issues when attempting to leverage this existing peering module, as the 100.64.0.0/16 routes will conflict in certain cases.
• One specific case is where we want to peer and route a single database or elasticsearch VPC to multiple different EKS cluster VPCs that all contain the 100.64.0.0/16 additional CIDR association

references

• https://aws.amazon.com/premiumsupport/knowledge-center/eks-multiple-cidr-ranges/

what and why

Change all references to git.io/build-harness into cloudposse.tools/build-harness, since git.io redirects will stop working on April 29th, 2022.

References

• DEV-143

what

• Removes the template provider from required_providers

why

• The template provider is deprecated by Hashicorp.
• Said provider appears to be unused in this module (it works perfectly fine without it).
• Trying to run Terraform on an M1 Mac with this module results in an error since the template provider does not have a darwin_arm64 build.

references

• https://github.com/hashicorp/terraform-provider-template/issues/85
• https://github.com/hashicorp/terraform/issues/27257

what

This is an auto-generated PR that updates the context.tf file to the latest version from cloudposse/terraform-null-label

why

To support all the features of the context interface.

what

• update context.tf to v0.24.1
• minimum required Terraform version bumped to 0.13.0
• readme updated, Bridgecrew compliance badges added

why

• It allows for setting the letter case of tag names and labels, back compatibility with context v0.22.0 and below
• we have dropped support for Terraform 0.12
• To be able see and fix the recommendations from Bridgecrew so we can position our modules as standards compliant

Supersedes and closes #29

what

• update context.tf to v0.23.0
• minimum required Terraform version bumped to 0.13.0
• readme updated, Bridgecrew compliance badges added

why

• It allows for setting the letter case of tag names and labels
• we have dropped support for Terraform 0.12
• To be able see and fix the recommendations from Bridgecrew so we can position our modules as standards compliant

what

• Upgrade to support Terraform 0.14 and bring up to current Cloud Posse standard

why

• Support Terraform 0.14

supersedes and closes #26