-
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
r/aws_rds_cluster
: Conflict snapshot_identifier
and global_cluster_identifier
#30158
r/aws_rds_cluster
: Conflict snapshot_identifier
and global_cluster_identifier
#30158
Conversation
Community NoteVoting for Prioritization
For Submitters
|
0846cf0
to
4edfba2
Compare
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.
The code change looks good. I got really stuck on the documentation for a couple reasons. First, the linked example was for a different case. Secondly, because the creation order of the RDS global cluster and region cluster is opposite from most other global clusters, such as ElastiCache, I was confused by the example.
3cd0424
to
736d002
Compare
This functionality has been released in v4.60.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
Triggers a conflict when both
snapshot_identifier
andglobal_cluster_identifier
are provided in the same configuration. It is not currently possible to restore from snapshot AND join an existing global cluster in a single operation. This plan time check prevents configurations which will succeed with unexpected results (see #29187).Relations
Closes #29187
References
Output from Acceptance Testing
NOTE: Failing tests do not appear related to this change.