terraform-aws-multi-az-subnets

what

• Add IPv6 subnet provisioning
• Assumes that the subnet created at the end must be a /64 (as per AWS).
• Only applies to public subnets. This could be added to private (with no default destination route ::/0) if others think this is necessary. There is no concept of NAT in AWS VPC IPv6.

why

• We have a requirement to offer dualstack workloads.
• Today we have to do this manually and if using this module, separate subnets need to be created.

references

• closes #43

🚀 Enhancements

what

The module is adding tags to all the resources except the EIP resource. We should add the same set of tags to that as well.

why

Adding tags to EIP resources has many advantages.

• Compliance requirement.
• Easy to understand the use by tags.

https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/eip#tags

🤖 Automatic Updates

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

No resource changes at all.
Add subnet_cidr_block to the output_map and az_subnet_cidr_blocks as an output.

why

This is helpful when you want to assign something like the 4th IP in a subnet rather than allowing DHCP to do it's thing.

references

n/a

what

• Do not require NAT gateway IDs for private subnets

why

• Users should be able to create subnets without NAT gateways
• Implemented in #48, which was closed in favor of #50, but #50 left this feature out

references

• Gateway Load Balancer patterns

🐛 Bug Fixes

what

• Fix #44 where setting nat_gateway_enabled=false caused an error
• Add test case for nat_gateway_enabled=false
• Supersedes and closes #48, thank you @paulrob-100 for the inspiration

why

• Bugfix

Not exactly a breaking change, but likely a disruptive one. The previous version was broken in its handling of the enabled flag. Upon review, we saw it was also fragile, dependent on the order in which you specified availability zones.

To fix these problems and for several other reasons, we switched from using count to enumerate resources that are allocated in each availability zone (AZ) to using for_each with the AZ name as the key. While this has many advantages going forward, it does mean that switching to this version will likely cause Terraform to try to destroy and recreate your subnets, which will fail if you have things provisioned in them. The structure of the Terraform has not changed substantially, so you can fix this by using terraform state rm and terraform import.

You might also take this opportunity to switch to using our more popular terraform-aws-dynamic-subnets module.

what

• Fix #46
• Incorporates, supersedes, and closes #45
• Incorporates, supersedes, and closes #41
• Add local availability_zones which is empty if disabled
  • private_count and public_count are either 0 if disabled or the length of the local.availability_zones list
  • therefore aws resource counts will not reference empty list in element function
  • also guaranteed to have same number of elements in zipmap function
• Added convenience local lists of tuples for outputs
• Note az_ngw_ids is now an empty map if disabled - previously a map of constant "0"
• dummy_az_ngw_ids is no longer referenced so remove
• Transform local lists of tuples to output maps
  • since private_count and public_count are not both >0, no ellipsis needed in transform, producing single map value
  • output maps are all empty if disabled

why

• Users should be able to set the enabled flag to false
• This is useful when used in conjunction with the terraform-yaml-stack-config module where subnets may be disabled but yaml configuration ready to flip the flag

references

• closes #46

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

🤖 Automatic Updates

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.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

🤖 Automatic Updates

what

This is an auto-generated PR that updates the README.md and docs

why

To have most recent changes of README.md and doc from origin templates

what

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

why

• Support Terraform 0.14

🤖 Automatic Updates

what

This is an auto-generated PR that updates the README.md and docs

why

To have most recent changes of README.md and doc from origin templates

🤖 Automatic Updates

This PR contains the following updates:

Release Notes

v0.22.1

Compare Source

what

• Upgrade to use context.tf, support Terraform 0.14, and bring up to current Cloud Posse standard

why

• Support advanced null-label features (some work still to be done)
• Support Terraform 0.14

notes

• The subnets are tagged with a "Name" tag that does not conform to null-label standards. It is left for backwards compatibility.

Closes #21, closes #29, closes #30

what

• set minimum versions for providers without pinning to a specific major version

why

• the current method makes it very difficult to maintain or upgrade consistent provider versions within a project

references

https://www.terraform.io/docs/configuration/provider-requirements.html#best-practices-for-provider-versions

what

• Port (rewrite) module with 0.12 syntax
• Update Codefresh badge to point to the test pipeline in terraform-modules project
• Update examples
• Update README
• Update README examples

why

• Module currently does not work with 0.12
• Much easier syntax
• terraform-modules project contains pipelines for all terraform modules