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 https://github.com/grem11n/terraform-aws-vpc-peering/pull/109
• Fix typo in examples/module-depends-on/README.md #104 by @kascodeo in https://github.com/grem11n/terraform-aws-vpc-peering/pull/105
• Allow to define the peering connection name as a variable by @uridium in https://github.com/grem11n/terraform-aws-vpc-peering/pull/106
• Migrate tests to Localstack by @grem11n in https://github.com/grem11n/terraform-aws-vpc-peering/pull/112
• Add Lint action by @grem11n in https://github.com/grem11n/terraform-aws-vpc-peering/pull/113
• Add routes for VPC + Subnet IPv6 space by @Unverified in https://github.com/grem11n/terraform-aws-vpc-peering/pull/116

New Contributors

• @herrbpl made their first contribution in https://github.com/grem11n/terraform-aws-vpc-peering/pull/109
• @kascodeo made their first contribution in https://github.com/grem11n/terraform-aws-vpc-peering/pull/105
• @uridium made their first contribution in https://github.com/grem11n/terraform-aws-vpc-peering/pull/106
• @Unverified made their first contribution in https://github.com/grem11n/terraform-aws-vpc-peering/pull/116

Full Changelog: https://github.com/grem11n/terraform-aws-vpc-peering/compare/v6.0.0...v7.0.0

Changes

• Allow the usage of 5.x.x version of the AWS Terraform provider: https://github.com/grem11n/terraform-aws-vpc-peering/pull/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.

Now, this module creates routes for additional CIDRs associated with VPCs as well, which fixed https://github.com/grem11n/terraform-aws-vpc-peering/issues/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 https://github.com/hashicorp/terraform/issues/28962#issuecomment-861596870 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 https://github.com/grem11n/terraform-aws-vpc-peering/pull/97
• Update Terraform version to the current latest in tests by @grem11n in https://github.com/grem11n/terraform-aws-vpc-peering/pull/99

Full Changelog: https://github.com/grem11n/terraform-aws-vpc-peering/compare/v5.0.0...v5.1.0

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.

• Provider lock is updated to support both 3.x.x and 4.x.x versions of the AWS provider: https://github.com/grem11n/terraform-aws-vpc-peering/pull/86
• Updated tests to check Terraform version > 1.1.x: https://github.com/grem11n/terraform-aws-vpc-peering/pull/88
• Updated README: https://github.com/grem11n/terraform-aws-vpc-peering/pull/87

• Terraform 0.15 support
• Use the Provider Aliases

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

• Terraform 0.15 support
• Use the Provider Aliases

Support for Terraform 0.15 with backward compatibility with 0.14

• Fixes depends_on issue (https://github.com/grem11n/terraform-aws-vpc-peering/issues/57)
• Added documentation regarding depends_on usage
• Run tests against Terraform 0.13 and 0.14
• Refactoring

• Updated Terraform version and Go version for the tests
• Fixed https://github.com/grem11n/terraform-aws-vpc-peering/issues/48
• Fixed https://github.com/grem11n/terraform-aws-vpc-peering/issues/52

• https://github.com/grem11n/terraform-aws-vpc-peering/pull/47 removes quoted lines, so deprecation notices are not triggered

• Added deprecation notice for Terraform 0.11
• Updated the tests

• Added a deprecation notice for Terraform 0.11
• Updated tests

Requires AWS provider version >=2.31.0!

• Deprecate DNS options workaround since https://github.com/terraform-providers/terraform-provider-aws/issues/6730 is fixed

Requires AWS provider version >=2.31.0!

• Deprecate DNS options workaround since https://github.com/terraform-providers/terraform-provider-aws/issues/6730 is fixed

• Implements change (https://github.com/grem11n/terraform-aws-vpc-peering/pull/35), which fixes (https://github.com/grem11n/terraform-aws-vpc-peering/issues/32) for Terraform version >= 0.12
• Migrate CI to GitHub Actions and tests refactoring

• Fix workaround for inter-region peering. See: this issue
• Tests for different peering scenarios
• Docs and examples updates

v1.2.0

• Create a test case for a single account, single region peering
• Add example configuration for a single account, single region peering, which is tested
• Updated README
• Marked value create_peering for deprecation
• Added test for cross-region peering in the same AWS account
• Fixed cross-region peering for TF < 0.12 version

Module version, which supports Terraform 0.12