resource/aws_elasticache_replication_group: support setting primary/replica AZ atrributes inside NodeGroupConfiguration for RedisClusterModelEnabled

[moose007]

Currently I do not have a way to express in an aws_elasticache_replication_group resource block which availability zone my primary node gets deployed in and which AZ its read replicas are deployed in. The AWS ElastiCache SDK supports the following attributes:

PrimaryAvailabilityZone

The Availability Zone where ElastiCache launches the node group's primary node.

Required: No

Type: String

ReplicaAvailabilityZones

A list of Availability Zones where ElastiCache launches the read replicas. The number of Availability Zones must match the value of the ReplicaCount property or, if you don't specify the ReplicaCount property, the replication group's ReplicasPerNodeGroup property.

Required: No

Type: List of String values

(see: https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-elasticache-replicationgroup-nodegroupconfiguration.html)

It would be useful for aws_elasticache_replication_group resource to provide the same level of control.

[moose007]

Some notes from @bflad:

For Redis Cluster Mode Enabled replication groups (e.g. when using cluster_mode in Terraform), we currently do not have the ability to set availability zones via the NodeGroupConfiguration parameter, which would likely require changing the cluster_mode argument. (from #5104)

[github-actions]

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!

[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!