[Enhancement]: Ability to switch from cluster mode disabled to compatible then on

[mwheeler-ep]

Description

The advice to enable cluster mode on a aws_elasticache_replication_group is to set the parameter group to one that has cluster mode enabled such as ones ending in .cluster.on, however this doesn't permit upgrading a cluster to cluster mode.

The parameter cluster-enabled has a different value in the requested parameter group than the current parameter group. This parameter value cannot be changed for a cache cluster

The upgrade can be performed in the console (tested), cli or via the API (untested but documented here https://docs.aws.amazon.com/AmazonElastiCache/latest/APIReference/API_ModifyReplicationGroup.html) by switching the cluster to compatible mode followed by on.

It would be good to be able to control the attribute so that migrations to cluster mode can be performed using terraform.

It's possible that I might be missing something that this option already exists through another mechanism? I believe the cluster_mode block was removed in favour of direct arguments. I don't think a block needs to be implemented to obtain this functionality.

Affected Resource(s) and/or Data Source(s)

aws_elasticache_replication_group

Potential Terraform Configuration

resource "aws_elasticache_replication_group" "example" {
  num_node_groups            = 1
  replicas_per_node_group    = 2
  parameter_group_name       = "default.redis7.cluster.on"
  cluster_mode               = "compatible"
}

References

https://docs.aws.amazon.com/AmazonElastiCache/latest/APIReference/API_ModifyReplicationGroup.html#ClusterMode
https://docs.aws.amazon.com/sdk-for-go/api/service/elasticache/#ModifyReplicationGroupInput

Would you like to implement a fix?

No

[github-actions]

Community Note

Voting for Prioritization

• Please vote on this issue by adding a 👍 reaction to the original post to help the community and maintainers prioritize this request.
• Please see our prioritization guide for information on how we prioritize.
• 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.

Volunteering to Work on This Issue

• If you are interested in working on this issue, please leave a comment.
• If this would be your first contribution, please review the contribution guide.

[AlexeyRaga]

Same issue, hope for a fix ;)

[github-actions]

Warning

This issue has been closed, meaning that any additional comments are hard for our team to see. Please assume that the maintainers will not see them.

Ongoing conversations amongst community members are welcome, however, the issue will be locked after 30 days. Moving conversations to another venue, such as the AWS Provider forum, is recommended. If you have additional concerns, please open a new issue, referencing this one where needed.

[github-actions]

This functionality has been released in v5.59.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. Thank you!

[github-actions]

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.