-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
r/aws_rds_cluster_instance: Treat storage-optimization
status as success when creating or updating cluster DB instances
#39691
Conversation
…BClusterInstanceUpdated' -> 'waitDBClusterInstanceAvailable'.
…ate (compare 'waitDBInstanceAvailable').
Community NoteVoting for Prioritization
For Submitters
|
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 🚀
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
storage-optimization
should be considered as a successful state when waiting for cluster instance create and update.The non-cluster instance resource,
aws_db_instance
, already has this behavior.Relations
Closes #38497
Output from Acceptance Testing