1.4.0
release causes issues with existing cluster where you don't want to enforce encryption in transit
#240
Labels
bug
🐛 An issue with the system
Describe the Bug
I have an existing cluster created with this module (created with version
0.52.0
). Tried to upgrade the module to version1.4.0
and that fails to apply the changes to replication group as encryption in transit isn't enforced:I'm not sure if this is a problem with AWS provider or with this module
Expected Behavior
Module version could be just updated and nothing breaks or requires a change. I think the
transit_encryption_mode
variable could be optional and not required.Steps to Reproduce
Create cluster with old module version, set
transit_encryption_enabled = false
with the module call and apply. Then try to update the module version to1.4.0
and nowtransit_encryption_mode
is set topreferred
by default and cannot be unset with the module. Even if I try to enable the encryption to have it enabled aspreferred
but notrequired
, it fails as the auth token cannot be updated.TF Plan:
And this results in a failure:
Screenshots
No response
Environment
Additional Context
No response
The text was updated successfully, but these errors were encountered: