-
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
New resource: aws_elasticache_global_replication_group #15885
New resource: aws_elasticache_global_replication_group #15885
Conversation
…lR/terraform-provider-aws into elasticache_global_replication_group
Hello, any idea when this wonderful PR will be merged? |
is there any way we can get some traction on this PR? |
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.
return fmt.Errorf("Elasticache Global Replication Group not found") | ||
} | ||
|
||
if aws.StringValue(cluster.Status) != "available" && aws.StringValue(cluster.Status) != "primary-only" { |
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.
Nice, this is a good check
resource "aws_elasticache_global_replication_group" "test" { | ||
global_replication_group_id_suffix = %q | ||
primary_replication_group_id = aws_elasticache_replication_group.test.id | ||
} |
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.
I like that you put the resource under test at the top. It makes it a lot easier to understand the test
Thanks @gdavison for your review. Let me know if I can help or review something :) |
This has been released in version 3.29.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 for triage. Thanks! |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks! |
Community Note
Relates #12708
Release note for CHANGELOG:
Output from acceptance testing:
Note:
In order to get a working ElastiCache Global Datastore, we should refine the resource elasticache_replication_group. Actually, to associate an elasticache_replication_group, the only parameter accepted is a global_replication_group_id. The change is pretty big on the resource elasticache_replication_group, so what do you recommend? Treating this in another PR?