-
-
Notifications
You must be signed in to change notification settings - Fork 58
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
Added VPN Tunnel Phase 1/2 Lifetimes #55
Conversation
d7db691
to
7fe4074
Compare
/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.
@jpschafer could you please fix the variable usage as suggested and run fmt
?
Co-authored-by: Veronika Gnilitska <[email protected]>
/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.
Thanks @jpschafer!
These changes were released in v1.5.0. |
@gberenice Just wanted to say thank you for helping me out in merging this and letting me contribute to this project. You all do great work! :) |
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.