Closed Zogoo closed 3 years ago
Currently I'm solving this issue with following way.
lifecycle {
ignore_changes = [engine_version]
}
This actually make sense since AWS team wants to manage minor versions for us. And I think no need to Terraform state hold this information anymore. If it would be solved by internal feature on Terraform that will be nice.
Duplicate to #15625?
Yes this looks like a duplicate of #15625
Closing as this appears to be a duplicate of a resolved issue.
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
Community Note
Terraform CLI and Terraform AWS Provider Version
Terraform: 0.12.26 AWS provider: 3.19
Affected Resource(s)
Debug Output
terraform plan
will show following outputPanic Output
terraform apply
fail with following messageExpected Behavior
Should apply without resource modification.
Actual Behavior
Failing with message mentioned in "Panic Output" part.
Steps to Reproduce
Any aws_elasticache_replication_group with REDIS 6.X version
terraform apply
Important Factoids
It seems like Terraform state hold version number after resource applied to AWS when first time create AWS environments. Second apply fail with because you cannot specify minor version of redis it self.
References
Any request with a specific version value will be rejected, an exception will be thrown and the process will fail.
https://docs.aws.amazon.com/AmazonElastiCache/latest/red-ug/supported-engine-versions.html#redis-version-6.x