If the resource is planned for an upgrade with a unsupported target version terraform should fail instead of resulting of a full cluster destroy / create operation.
Actual Behavior
If the target version is not listed as compatible the provider instructs terraform to delete the resource first and then create a new cluster with the target version resulting on a full cluster recreation. This is usually not what users want.
Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.
Volunteering to Work on This Issue
If you are interested in working on this issue, please leave a comment.
If this would be your first contribution, please review the contribution guide.
Terraform Core Version
1.9.5
AWS Provider Version
5.66.0
Affected Resource(s)
Expected Behavior
If the resource is planned for an upgrade with a unsupported target version terraform should fail instead of resulting of a full cluster destroy / create operation.
Actual Behavior
If the target version is not listed as compatible the provider instructs terraform to delete the resource first and then create a new cluster with the target version resulting on a full cluster recreation. This is usually not what users want.
Relevant Error/Panic Output Snippet
No response
Terraform Configuration Files
Steps to Reproduce
OpenSearch_1.0
elasticsearch_version
fromOpenSearch_1.0
toOpensearch_1.3
( note that there is a typo in the target version )Debug Output
No response
Panic Output
No response
Important Factoids
No response
References
No response
Would you like to implement a fix?
Yes