-
-
Notifications
You must be signed in to change notification settings - Fork 60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: adds tagging the TGW attachment + associating / propagating TGW RTB + creating TGW routes #37
Conversation
…ol > string) I could not find why this was originally implemented this way... Maybe a 0.11 holdover? It was bugging me.
… RTB + creating TGW routes
/terratest |
Submitting this as a
|
/terratest |
/terratest |
/terratest |
/terratest |
1 similar comment
/terratest |
/terratest |
/terratest |
/terratest |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks @Gowiem
* upstream/main: feat: adds tagging the TGW attachment + associating / propagating TGW RTB + creating TGW routes (cloudposse#37) Update README.md and docs (cloudposse#31) Sync github (cloudposse#29) Feature: Multiple VPCs through single site-to-site VPN with transit gateway id (cloudposse#27)
major
revisionThis 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 as1.0
.what
var.vpn_connection_static_routes_only
var.vpc_id
being required as this should not be required with TGW VPN Connectionnull
providervpn_connection_customer_gateway_configuration
tosensitive = true
transit_gateway_attachment_id
as an outputwhy
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.optional
invar.transit_gateway_routes
)null
provider no longer needed - Likely a holdout from an old version ofterraform-null-label
(this module had some dust on it)references