Skip to content
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

Can’t assign a secondary elasticache replication group to a global elasticache replication group #17812

Closed
OmarSalka opened this issue Feb 25, 2021 · 3 comments · Fixed by #17725
Assignees
Labels
enhancement Requests to existing resources that expand the functionality or scope. service/elasticache Issues and PRs that pertain to the elasticache service.
Milestone

Comments

@OmarSalka
Copy link

Hi,

I couldn’t find a way to assign a secondary replication group to a global replication group. There isn’t an attribute for global_replication_group_id that I can provide to the replication group. However, the CLI has this attribute which can be used to attach a secondary replication group to a global one. Am I missing something?

@github-actions github-actions bot added the needs-triage Waiting for first response or review from a maintainer. label Feb 25, 2021
@bflad bflad added enhancement Requests to existing resources that expand the functionality or scope. service/elasticache Issues and PRs that pertain to the elasticache service. and removed needs-triage Waiting for first response or review from a maintainer. labels Mar 1, 2021
@bflad
Copy link
Contributor

bflad commented Mar 1, 2021

It appears this may be covered by #17725

@ghost
Copy link

ghost commented Mar 12, 2021

This has been released in version 3.32.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!

@ghost
Copy link

ghost commented Apr 11, 2021

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!

@ghost ghost locked as resolved and limited conversation to collaborators Apr 11, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement Requests to existing resources that expand the functionality or scope. service/elasticache Issues and PRs that pertain to the elasticache service.
Projects
None yet
3 participants