Add `primary_cluster_id` support for `aws_elasticache_replication_group` resource

[bmbferreira]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

Currently I have an existing single-node Redis cluster and I want to create a replication group in order to add more instances in different AZs to implement fault tolerance of the cluster. I was trying to following the AWS documentation for this use case but I just noticed on Terraform documentation for aws_elasticache_replication_group resource that the primary_cluster_id is not supported, which according to AWS docs previously referred, is required to create a replication group and associate it with an existing single-node Redis cluster.

So, my questions are:

1. Is this going to be supported in the near future?
2. Is there an alternative that does not require the creation of a new cluster from scratch?

New or Affected Resource(s)

• aws_elasticache_replication_group

Potential Terraform Configuration

N/A

References

N/A

[github-actions[bot]]

Marking this issue as stale due to inactivity. This helps our maintainers find and focus on the active issues. If this issue receives no comments in the next 30 days it will automatically be closed. Maintainers can also remove the stale label.

If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thank you!

[github-actions[bot]]

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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.