-
Notifications
You must be signed in to change notification settings - Fork 9.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
resource/aws_elasticache_replication_group: Support Cluster Mode Enabled online shard reconfiguration #3932
resource/aws_elasticache_replication_group: Support Cluster Mode Enabled online shard reconfiguration #3932
Conversation
…led online shard reconfiguration * Properly read cluster_mode back into Terraform state * Improves cluster_mode update plan output by migrating state from TypeSet to TypeList * Allows configurable timeouts for create, delete, and update
…usters check in TestAccAWSElasticacheReplicationGroup_ClusterMode_NumNodeGroups
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A couple of minor points but this otherwise LGTM 👍🏼
} | ||
} else { | ||
d.Set("cluster_mode", []interface{}{}) | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
minor this logic could live within the flatten function tbh?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Its a little awkward because in order to keep backwards compatibility we have to use the other attribute. I can move it though.
replicas_per_node_group = 1 | ||
num_node_groups = 2 | ||
num_node_groups = %[2]d | ||
replicas_per_node_group = %[3]d |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There’s a bug in govet where it won’t raise an error for these if you’re using the numbered index, but will if you’re using them as the actual type eg “%d” (when specifying the wrong type). Up to you, but I’d suggest there’s value in listing these variables explicitly (or by assigning them to a Terraform variable above and referencing that) so that these errors are raised?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wish I could fix that bug. 😉 For now I'll revert back to non-indexed references.
This has been released in version 1.14.0 of the AWS provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. |
…ed online shard reconfiguration hashicorp#3932
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! |
Closes #2904