Skip to content

Releases: cloudposse/terraform-aws-transit-gateway

v0.11.2

11 Mar 08:44
0dfe8cd
Compare
Choose a tag to compare
Configurable timeoutes @hans-d (#40)

what

  • Replace hardcoded (but default) timeout for aws_route with configurable one

why

  • more flexibilty needed re tiemouts

🤖 Automatic Updates

Update Scaffolding @osterman (#39)

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

v0.11.1

07 Mar 18:58
5c05105
Compare
Choose a tag to compare

🚀 Enhancements

Updating default value description to match actual default value @joshuabalduff (#26)

what

default_route_table_association and default_route_table_propagation are set to disable so the description should reflect default values that to avoid possible confusion.

why

So it matches :) unless the default value really should be enable

references

🤖 Automatic Updates

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

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

21 Jun 15:45
9126c9e
Compare
Choose a tag to compare
Support AWS Provider V5 @max-lobur (#35)

what

Support AWS Provider V5
Linter fixes

why

Maintenance

references

https://github.com/hashicorp/terraform-provider-aws/releases/tag/v5.0.0

Sync github @max-lobur (#33)

Rebuild github dir from the template

v0.10.0

17 May 09:04
dc12987
Compare
Choose a tag to compare
  • No changes

v0.9.1

30 May 08:55
dc12987
Compare
Choose a tag to compare
git.io->cloudposse.tools update @dylanbannon (#21)

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

🚀 Enhancements

Bump aws provider to v4.4.0 @nitrocode (#23)

what

  • Bump aws provider to v4.4.0

why

  • Prevent people from using an older provider version which would cause issues

references

v0.9.0

01 Apr 01:45
dd741e0
Compare
Choose a tag to compare
Support multiple RAM principals @alexjurkiewicz (#19)

Introduce new variable var.ram_principals, and deprecate
var.ram_principal. Deprecating rather than removing the old variable is
a lot more complex, code-wise, but the complexity is contained and
should ease the upgrade path for existing customers.

Fixes #14

v0.8.0

29 Mar 00:03
c31ec16
Compare
Choose a tag to compare
Allow manually specifying Transit Gateway description @alexjurkiewicz (#18)

v0.7.0

28 Mar 16:54
6ae39e7
Compare
Choose a tag to compare
Add var.transit_gateway_cidr_blocks @alexjurkiewicz (#20)

v0.6.1

14 Dec 17:43
ef27722
Compare
Choose a tag to compare

🚀 Enhancements

Output `ram_resource_share_id` @nitrocode (#17)

what

  • Output ram_resource_share_id

why

  • In case additional principals need to be associated to the ram resource share
  • At the moment, if var.ram_principal is passed in, the org data source is replaced, and there is no way to pass in multiple ram principals
  • Easiest solution is to export the ram resource share id and associate from outside the module

references

v0.6.0

03 Dec 00:44
4064307
Compare
Choose a tag to compare
Add VPC attachment appliance mode support @lgallard (#16)

what

  • Add VPC attachment appliance mode support

why

  • To enable traffic flow between source and destination in the same Availability Zone for the VPC attachment for the lifetime of that flow.

references