-
Notifications
You must be signed in to change notification settings - Fork 9.2k
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
[Bug]: Getting operation error ElastiCache while modifying storage for aws_elasticache_serverless_cache #39711
Comments
Community NoteVoting for Prioritization
Volunteering to Work on This Issue
|
Good evening @Chandan-Nayak! I can confirm that it can be reproduced with version 5.71.0 of the Terraform provider. I used below code in combination with the provider and Terraform version 1.9.3.
Out of curiosity I tried the older provider version 5.70.0 and did not run into the issue. If you can spare a few minutes, could you please test and confirm from your end? Valkey support for Elasticache was added by AWS last week and there another open issue related to Elasticache and Valkey support: #39641 |
@stefanfreitag Thank you for a quick response. |
There is one difference I spotted between the two provider versions
In the AWS SDK GO v2 I found for // Modifies the engine listed in a serverless cache request. The options are
// redis, memcached or valkey.
Engine *string
// Modifies the engine vesion listed in a serverless cache request.
MajorEngineVersion *string as input to the |
…ache Fixes hashicorp#39711 Signed-off-by: Aurel Canciu <aurel.canciu@nexhealth.com>
We are getting the same error in CI:
It looks like #39745 fixes this, so I think we'll prioritize that PR. |
Warning This issue has been closed, meaning that any additional comments are hard for our team to see. Please assume that the maintainers will not see them. Ongoing conversations amongst community members are welcome, however, the issue will be locked after 30 days. Moving conversations to another venue, such as the AWS Provider forum, is recommended. If you have additional concerns, please open a new issue, referencing this one where needed. |
This functionality has been released in v5.73.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you! |
Terraform Core Version
1.4.6
AWS Provider Version
5.71.0
Affected Resource(s)
A aws_elasticache_serverless_cache resource is created with storage 10 GB.
Creation is done and I want to modify the storage to 20 GB.
Terraform apply produces below mentioned error
Steps to reproduce
Expected Behavior
Terraform should be able to apply the change successfully
Actual Behavior
Getting below error
Relevant Error/Panic Output Snippet
No response
Terraform Configuration Files
Steps to Reproduce
Steps to reproduce
Debug Output
No response
Panic Output
No response
Important Factoids
No response
References
No response
Would you like to implement a fix?
No
The text was updated successfully, but these errors were encountered: