v7.0.1

This release contains a fix for the Name tag (#111) as well as some improvements to the tests.

This is a minor patch, but depending on your tags configuration and any workarounds applied for #111, your tags for the peering may be re-created.

What's Changed

• Fix broken name tag by @grem11n in #119
• Update TF version for tests by @grem11n in #120
• Run tests in parallel by @grem11n in #121

Full Changelog: v7.0.0...v7.0.1

v7.0.0

v7.0.0

It's been some time since the previous release, so bumping the major version just in case. Otherwise, there should be no breaking changes compared to the previous release.

What's Changed

• This is a fix for #108 by @herrbpl in #109
• Fix typo in examples/module-depends-on/README.md #104 by @kascodeo in #105
• Allow to define the peering connection name as a variable by @uridium in #106
• Migrate tests to Localstack by @grem11n in #112
• Add Lint action by @grem11n in #113
• Add routes for VPC + Subnet IPv6 space by @Unverified in #116

New Contributors

• @herrbpl made their first contribution in #109
• @kascodeo made their first contribution in #105
• @uridium made their first contribution in #106
• @Unverified made their first contribution in #116

Full Changelog: v6.0.0...v7.0.0

Allow the usage of the AWS Provider 5.x.x

Changes

• Allow the usage of 5.x.x version of the AWS Terraform provider: #103

Considerations

The new version should work with AWS Terraform Provider 4.x.x as well. Yet, to avoid unexpected behavior, I'm releasing this as a new major version of the module.

Create routes for additional CIDRs

Now, this module creates routes for additional CIDRs associated with VPCs as well, which fixed #94.

API Changes

This release exposes two new user variables:

• from_this_associated to create routes for additional CIDRs from this VPC
• from_peer_associated to create routes for additional CIDRs from peer VPC

Considerations

The module still relies on additional variables to create routes for associated CIDRs. However, based on hashicorp/terraform#28962 (comment) I assume it's impossible to calculate routes for associated CIDRs unless VPC configuration already exists. This means that depends_on directive probably won't work with additional VPC CIDRs, if you want to create the whole infrastructure in one swing. Yet, I haven't tested that scenario.

Code Changes

• Create routes for associated VPC CIDRs by @grem11n in #97
• Update Terraform version to the current latest in tests by @grem11n in #99

Full Changelog: v5.0.0...v5.1.0

AWS Classic Deprecation

Major changes

• AWS Classic is going to be deprecated. Therefore, related options were deprecated as well PR#92. Fixes: Issue#91

Other changes

• Removed CHANGELOG.md file since it was not well-maintained PR#93.
• Update versions of Go and Terraform for the tests PR#93.
• Removed some leftovers of the CI integration for Terraform 0.11 PR#93.
• Fixes in the documentation PR#90.

Tests for Terraform > 1.1.x and AWS Provider > 4.x.x

• Provider lock is updated to support both 3.x.x and 4.x.x versions of the AWS provider: #86
• Updated tests to check Terraform version > 1.1.x: #88
• Updated README: #87

Pin the minimum Terraform version

• Pinned the minimum required Terraform version
• Updated tests with more stable regions
• Bug report template

Terraform 0.15 support

• Terraform 0.15 support
• Use the Provider Aliases

Terraform 0.15 support

Support for Terraform 0.15 with backward compatibility with 0.14

Terraform 0.15 support

• Terraform 0.15 support
• Use the Provider Aliases