-
-
Notifications
You must be signed in to change notification settings - Fork 54
fix: Enable transit_encryption_enabled
for all avialble engines now that Elasticache supports this
#56
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
Conversation
transit_encryption_enabled
for all engines
transit_encryption_enabled
for all enginestransit_encryption_enabled
for all avialble engines now that Elasticache supports this
## [1.10.1](v1.10.0...v1.10.1) (2025-10-07) ### Bug Fixes * Enable `transit_encryption_enabled` for all avialble engines now that Elasticache supports this ([#56](#56)) ([2ee85ee](2ee85ee))
This PR is included in version 1.10.1 🎉 |
This was supposed to be released as a breaking change. As soon the module version was updated, clusters were trying to be recreated because of this default variable.
|
…gines now that Elasticache supports this terraform-aws-modules#56
apologies for that - the removal of the prior restriction appears to clash with the current default behavior of the module to enforce encryption we'll revert for now in #57 and save this change for an upcoming breaking change that will be released under a new major version number |
Description
Support transit_encryption_enabled for all Engines
Motivation and Context
transit_encryption_enabled
was disabled by default for Redis Engine.Resolves #55
Breaking Changes
No
How Has This Been Tested?
examples/*
to demonstrate and validate my change(s)examples/*
projectspre-commit run -a
on my pull request