resource/aws_elasticache_replication_group: Migrate from availability_zones
TypeSet attribute to preferred_cache_cluster_azs
TypeList attribute
#18438
Labels
service/elasticache
Issues and PRs that pertain to the elasticache service.
technical-debt
Addresses areas of the codebase that need refactoring or redesign.
Milestone
Community Note
Description
When creating a Redis cluster without sharding ("Cluster Mode Disabled" in AWS terminology), it is possible to specify a list of availability zones in which to place the cluster nodes. In the AWS API, the order of the list matters: the first AZ in the list is the primary AZ for the cluster, and the remainder of the nodes are assigned in order. The number of AZs in the list must match the number of nodes, and duplicates are allowed.
As currently implemented in the AWS Provider, the parameter
availability_zones
is ofTypeSet
, where order is not guaranteed and duplicates are not permitted. This means that the practitioner has no control over the location of the primary node and there can be at most one node in a given AZ.Additionally, the current parameter name,
availability_zones
, does not match the AWS API parameter namePreferredCacheClusterAZs
.A new parameter
preferred_cache_cluster_azs
ofTypeList
should be added toaws_elasticache_replication_group
. Changes toaws_elasticache_replication_group
should not be markedForceNew
, as the primary AZ, the order of AZs, and the number of AZs can be changed in-place.availability_zones
will be removed as part of #18439.Specifying AZs for sharded ("Cluster Mode Enabled" in AWS terminology) clusters is described in #5118.
References
The text was updated successfully, but these errors were encountered: