-
-
Notifications
You must be signed in to change notification settings - Fork 249
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: Allow configuring transit_encryption_mode #231
feat: Allow configuring transit_encryption_mode #231
Conversation
These changes were released in v1.4.0. |
/terratest |
@amontalban tests are failing:
Could you please update values in |
/terratest |
/terratest |
|
/terratest |
/terratest |
/terratest |
I was able to fix the tests. Please rebuild the readme with the addition of the variable. |
@amontalban LGTM apart from the readme rebuild 👍 |
💥 This pull request now has conflicts. Could you fix it @amontalban? 🙏 |
Thanks @nitrocode 🙏 @Laakso README has been updated. |
/terratest |
One thing we forgot to do was bump the minimum aws provider version to 5.47.0 in versions.tf |
Setting this argument to I have module deployment that has
|
Also I have number of existing redis clusters with engine version |
Hey @z0rc thank you for catching that issue, I was blindsided with my use case that I forgot to test it with it. I have created #238, can you check if it works with that, please? Thanks! |
I have exactly the same issue. (
|
what
Allow configuring
transit_encryption_mode
.why
This was added in AWS Provider v5.47.0 as part of hashicorp/terraform-provider-aws#30403
This is needed if you want to migrate to in-transit encryption with no downtime.
references