Community Note

Voting for Prioritization

• Please vote on this issue by adding a 👍 reaction to the original post to help the community and maintainers prioritize this request.
• Please see our prioritization guide for information on how we prioritize.
• 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.

from terraform-provider-aws.

Relates #33867

from terraform-provider-aws.

Hey @shettypriy 👋 Thank you for taking the time to raise this! Are you able to supply debug logs (redacted as needed) in case whoever looks into this needs that information?

from terraform-provider-aws.

hi @justinretzolk I am also facing exact same issue , Kindly let me know how to gather the debug log and share with you

from terraform-provider-aws.

I'm hitting this as well, here's my lockfile https://gist.github.com/darkhelmet/7689bd5928d5832b75b4970a2aef6ee9

I've already updated the Redis instance to 7.1 via the console, and this is now just running plan after I've updated my TF

from terraform-provider-aws.

I encountered the same issue while updating my Terraform AWS provider. My Redis cache instances were originally created using AWS provider version 3, and the engine version I used was specified as "7.x". When I attempted to update the provider to the latest version (5.54.1), I encountered the error related to parsing the engine_version.

To resolve this issue, I initially fixed it by manually modifying the tfstate file. However, this approach is not scalable for my projects because I have a large number of Redis cache instances, making it impractical to edit each tfstate file individually.

from terraform-provider-aws.