#2218 Allow adding/removing of ElastiCache Clusters to an existing ElastiCache Replication Group

[delphyne]

Hello all, I'm looking for feedback on this PR. This covers issue #2218. The current provider implementation requires updates to the number_cache_clusters property of the aws_elasticache_replication_group resource. This is a "force new" operation, which means you cannot dynamically scale your cluster.

[delphyne]

@radeksimko any motion on this? are there any issues that you wish to have addressed?

[bflad]

Hi @delphyne 👋 We're really sorry no one got back to you sooner about this pull request. It was mostly in good shape except for needing acceptance testing, some additional documentation, and addressing the interface conversion panics. We had some internal priority for finishing this up so I went ahead and submitted a continuation PR (with your commits in tact 😄 ) at #3869. It should land into master in the next few days and release with v1.12.0 of the AWS provider.

Again, thanks so much for your contribution. We're looking at ways we can reduce the review/merge lag for enhancement pull requests like this one.

[delphyne]

Thanks @bflad.

this PR replaced and extended by PR #3869

[ghost]

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!