v0.8.0

Feature: Multiple VPCs through single site-to-site VPN with transit gateway id @matharoo (#27)

what

• This PR adds ability to add transit-gateway id to the site to site vpn, with which we can attach multiple vpcs to one site-to-site vpn.
• By default it will create the site-to-site vpn with Vitrual private gateway the way it does now.
• With this PR we give the option to pass transit_gateway_enabled to set to true then we can pass in existing_transit_gateway_id then it will setup the VPN with transit-gateway. By default transit_gateway_enabled is set to false and the module sets up the Virtual Private gateway.

why

• Currently we cannot setup a VPN with transit gateway id, we can only setup with vpn virtual private gateway which is only attached to one 1 VPC.
• With Transit gateway we can attach multiple VPC's and subnets to one transit gateway id and then specify that id in transit_gateway_id in resource aws_vpn_connection

references

• This PR closes #28

git.io->cloudposse.tools update @dylanbannon (#20)

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

v0.7.1

🤖 Automatic Updates

Update context.tf @cloudpossebot (#18)

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.

v0.7.0

feat: adds new optional arguments @gberenice (#16)

what

• Adds optional arguments for aws_vpn_connection.

why

• This allows to configure various S2S VPN Connection tunnel options (algorithms, preshared keys, DH group numbers etc).
• These arguments are supported by provider, but not in the module.

references

• N/A

v0.6.0

context.tf updated to v0.24.1, minimum required Terraform version bumped to 0.13.0 when needed, readme updated @maximmi (#13)

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

v0.5.1

🤖 Automatic Updates

Update README.md and docs @cloudpossebot (#15)

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

v0.5.0

Terraform 0.14 upgrade @maximmi (#11)

what

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

why

• Support Terraform 0.14

v0.4.2

🚀 Enhancements

Terraform 0.14 upgrade @maximmi (#9)

what

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

why

• Support Terraform 0.14

Supersedes and closes #8
Supersedes and closes #10

0.4.1

[AUTOMATED] Update terraform-null-label versions to support Terraform…

0.4.0: [AUTOMATED] Update Version Pinning for Terraform to support 0.13 (#5)

1. Update Version Pinning for Terraform to support 0.13

1. This is a relatively minor update that the CloudPosse module already likely supports.
1. This allows module consumers to not individually update our Terraform module to support Terraform 0.13.

0.3.0: Updates to ChatOps - Automated commit (#4)

## What
* Adds chatops commands
  - '/test all'
  - '/test bats'
  - '/test readme'
  - '/test terratest'
* Drops codefresh
* Drops slash-command-dispatch
* Removes codefresh badge
* Rebuilds README

## Why
* Change over from codefresh to GH Actions
* Facilitate testing of PRs from forks