v1.7.0

Add variable for customer gateway device name @oc-christopher-billett (#57)

## what

Set the customer gateway device name to be a variable

why

To stop it rebuilding on existing VPN's with it not set

references

closes #56

v1.6.0

🐛 Bug Fixes

fix: support for 32-bit ASN @riccardolocci (#52)

The variable `customer_gateway_bgp_asn` now automatically sets `bgp_asn` or `bgp_asn_extended` whether the value cannot be represented as a 32-bit number

what

This PR adds support for ASN numbers greater than 2147483647

why

Customer Gateways created by the module only use variable bgp_asn, which does not support 32-bit integers
Instead the aws_customer_gateway resource provides a different variable, bgp_asn_extended which is not currently used by the module

references

hashicorp/terraform-provider-aws#38738

v1.5.0

Added VPN Tunnel Phase 1/2 Lifetimes @jpschafer (#55)

## what

Added Tunnel 1/2 Phase 1/2 Lifetime Variables

why

So I can add custom lifetimes outside of the defaults for customers who have different lifetimes set for their end of the tunnel.

references

#54

https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/vpn_connection#tunnel1_phase1_lifetime_seconds

The only issue to note is that in the AWS Console, you will see 28800 and 3600 respectively instead of "default" for each. I wasn't sure If that really matters but it's the only issue I could think of. I'm open to suggestions on preferences regarding this variable that is technically optional. I wasn't sure if setting it to null would create the same behavior.

v1.4.0

fix: added create_before_destroy argument for customer gateway @riccardolocci (#53)

## what

Added meta-argument lifecycle to aws_customer_gateway.default to create the resource before it gets destroyed when an argument update generates a resource replacement

why

If the customer gateway needs to be replaced (for example, when attributes bgp_asn or device_name change), Terraform is unable to delete the resource because it is being used by the VPN connection and its updated substitute is not created beforehand:

aws_customer_gateway.default[0]: Destroying... [id=cgw-XXXXXXXXXXXXXXXXX]
╷
│ Error: deleting EC2 Customer Gateway (cgw-XXXXXXXXXXXXXXXXX): operation error EC2: DeleteCustomerGateway, https response error StatusCode: 400, RequestID: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx, api error IncorrectState: The customer gateway is in use.

v1.3.1

Bugfix: `transit_gateway_enabled` is true resource routetable propagation null value @Benbentwo (#51)

## what

• Bugfix when variable transit_gateway_enabled is true

why

• Resource that shouldn't be created was

🤖 Automatic Updates

Migrate new test account @osterman (#50)

## what - Update `.github/settings.yml` - Update `.github/chatops.yml` files

why

• Re-apply .github/settings.yml from org level to get terratest environment
• Migrate to new test account

References

• DEV-388 Automate clean up of test account in new organization
• DEV-387 Update terratest to work on a shared workflow instead of a dispatch action
• DEV-386 Update terratest to use new testing account with GitHub OIDC

v1.3.0

Update to latest module versions. Update tests @aknysh (#49)

## what

• Update to latest module versions
• Format terraform code
• Update Go version for tests
• Update tests

why

• Keep up to date

v1.2.0

Allow nullification of `customer_gateway_ip_address` @LawrenceWarren (#39)

## what

• Allow the nullification of customer_gateway_ip_address
• If this is done, certain resources that are created by default will not be created

why

• This module creates a range of VPN Gateway resources
• 3 of them are created by default
  • aws_vpn_gateway.default
  • aws_customer_gateway.default
  • aws_vpn_connection.default
• However, some use cases may not need the customer gateway or the VPN connection
• For example, some VPN Gateways may be used in conjunction with virtual interfaces to allow VPN to VPN communication

🤖 Automatic Updates

Update .github/settings.yml @osterman (#48)

## what - Update `.github/settings.yml` - Drop `.github/auto-release.yml` files

why

• Re-apply .github/settings.yml from org level
• Use organization level auto-release settings

references

• DEV-1242 Add protected tags with Repository Rulesets on GitHub

Update release workflow to allow pull-requests: write @osterman (#47)

## what - Update workflow (`.github/workflows/release.yaml`) to have permission to comment on PR

why

• So we can support commenting on PRs with a link to the release

Update GitHub Workflows to use shared workflows from '.github' repo @osterman (#46)

## what - Update workflows (`.github/workflows`) to use shared workflows from `.github` repo

why

• Reduce nested levels of reusable workflows

Update GitHub Workflows to Fix ReviewDog TFLint Action @osterman (#44)

## what - Update workflows (`.github/workflows`) to add `issue: write` permission needed by ReviewDog `tflint` action

why

• The ReviewDog action will comment with line-level suggestions based on linting failures

Update GitHub workflows @osterman (#43)

## what - Update workflows (`.github/workflows/settings.yaml`)

why

• Support new readme generation workflow.
• Generate banners

Use GitHub Action Workflows from `cloudposse/.github` Repo @osterman (#42)

## what

• Install latest GitHub Action Workflows

why

• Use shared workflows from cldouposse/.github repository
• Simplify management of workflows from centralized hub of configuration

Add GitHub Settings @osterman (#41)

## what - Install a repository config (`.github/settings.yaml`)

why

• Programmatically manage GitHub repo settings

v1.1.0

🚀 Enhancements

feat: add logging options @esolitos (#26)

what

Implemented ability to set log to cloudwatch.

• Added cloudposse/cloudwatch-logs/aws to create a logging group
• Added vpn_connection_tunnel1_cloudwatch_log_enabled and vpn_connection_tunnel2_cloudwatch_log_enabled to allow enabling logging for a specific tunnel
• Added vpn_connection_log_retention_in_days to allow configuring logs retention
• Ran make actions to sync, as recommended in another PR.

why

This allow enabling logging on the tunnels, which was not possible before.

references

• closes #24

🤖 Automatic Updates

Update Scaffolding @osterman (#38)

what

• Reran make readme to rebuild README.md from README.yaml
• Migrate to square badges
• Add scaffolding for repo settings and Mergify

why

• Upstream template changed in the .github repo
• Work better with repository rulesets
• Modernize look & feel

v1.0.0

Sync github @max-lobur (#29)

Rebuild github dir from the template

🚀 Enhancements

feat: adds tagging the TGW attachment + associating / propagating TGW RTB + creating TGW routes @Gowiem (#37)

major revision

This PR does a good overhaul of the module: It updates to modern practices / syntax + uses new syntax added in TF 1.3 + adds some new, significant functionality + introduces a breaking change (changes var from string => bool type). Considering that, I believe we should release this as 1.0.

what

• Adds tagging the TGW attachment
• Adds associating + propagating the TGW attachment if TGW route table given
• Adds ability to create TGW routes on the given route table
• Fixes the type of var.vpn_connection_static_routes_only
• Fixes var.vpc_id being required as this should not be required with TGW VPN Connection
• Updates to require TF 1.3 and above
• Removes the null provider
• Updates vpn_connection_customer_gateway_configuration to sensitive = true
• Adds transit_gateway_attachment_id as an output

why

• Adds more flexibility + usefulness when working with a TGW <> VPN connection
• var.vpn_connection_static_routes_only - Types should be correct, so this was bugging me. Is this possibly a 0.11 holdout that we're finding in 2024? I didn't check the blame, but that'd be funny.
• Requires 1.3+ TF purely because this should be a 1.0 of this module and I think we should start using new functionality (required here as I used optional in var.transit_gateway_routes)
• null provider no longer needed - Likely a holdout from an old version of terraform-null-label (this module had some dust on it)

references

• Fixes #36 which was causing tests to fail
• Fixes #35
• Fixes #32

🤖 Automatic Updates

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

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

• No changes