-
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
Fix aws_elasticache_replication_group recreation on import #39591
Fix aws_elasticache_replication_group recreation on import #39591
Conversation
Community NoteVoting for Prioritization
For Submitters
|
1b66e92
to
79e99e9
Compare
79e99e9
to
2b40700
Compare
…to fix 'Cannot find version 5.0.4 for redis'.
…annot find version 5.0.4 for redis'.
Thank you for your contribution! 🚀 Please note that typically Go dependency changes are handled in this repository by dependabot or the maintainers. This is to prevent pull request merge conflicts and further delay reviews of contributions. Remove any changes to the Additional details:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 🚀.
--- PASS: TestAccElastiCacheReplicationGroup_basic (787.78s)
--- PASS: TestAccElastiCacheReplicationGroup_basic_v5 (787.82s)
--- PASS: TestAccElastiCacheReplicationGroup_vpc (818.80s)
@vtstanescu Thanks for the contribution 🎉 👏. |
This functionality has been released in v5.72.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! |
I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Description
Fix issue causing
aws_elasticache_replication_group
to be recreated after import.Relations
Closes #32835
References
Output from Acceptance Testing
No new acceptance test was created. I'm not sure how to make one to test the import workflow and assert that the resource is not replaced afterwards.