-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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_cluster: Migrate from availability_zones TypeSet attribute to preferred_availability_zones TypeList attribute #4741
Conversation
…eSet attribute to preferred_availability_zones TypeList attribute
… and use preferred_availability_zones in multi-az test
@@ -180,6 +180,9 @@ func resourceAwsElasticacheCluster() *schema.Resource { | |||
ForceNew: true, | |||
} | |||
|
|||
resourceSchema["availability_zones"].ConflictsWith = []string{"preferred_availability_zones"} |
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 have created #4828 to fully expand the resource schemas rather than continue with this generated approach.
This has been released in version 1.23.0 of the AWS provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. |
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! |
Fixes #2658
Fixes #374
Fixes #207
Changes proposed in this pull request:
availability_zones
(TypeSet) attribute inaws_elasticache_cluster
preferred_availability_zones
(TypeList) attribute inaws_elasticache_cluster
NewAvailabilityZones
parameter inModifyCacheCluster
when increasingnum_cache_nodes
withpreferred_availability_zones
num_cache_nodes
while utilizingpreferred_availability_zones
We must create a new attribute because there is no way to migrate state from TypeSet to TypeList without breaking existing configurations, so we will allow an opt-in upgrade procedure and phase out the old attribute. I'm indifferent with the new attribute naming so suggestions welcome (we've used
ordered_X
for other migrations like this, butpreferred_
here does match theCreateCacheCluster
parameterPreferredAvailabilityZones
).Output from acceptance testing: