Skip to content

Commit eed48c1

Browse files
NA2047melinath
andauthored
Breaking Change: Remove allow_fewer_zones_deployment from Memorystore and Redis Cluster (#14889)
Co-authored-by: Stephen Lewis (Burrows) <stephen.r.burrows@gmail.com>
1 parent e2e1d51 commit eed48c1

5 files changed

Lines changed: 8 additions & 18 deletions

File tree

mmv1/products/memorystore/Instance.yaml

Lines changed: 0 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -517,14 +517,6 @@ properties:
517517
enum_values:
518518
- 'MULTI_ZONE'
519519
- 'SINGLE_ZONE'
520-
- name: 'allowFewerZonesDeployment'
521-
type: Boolean
522-
description: |
523-
Allows customers to specify if they are okay with deploying a multi-zone
524-
instance in less than 3 zones. Once set, if there is a zonal outage during
525-
the instance creation, the instance will only be deployed in 2 zones, and
526-
stay within the 2 zones for its lifecycle.
527-
immutable: true
528520
- name: 'deletionProtectionEnabled'
529521
type: Boolean
530522
description: "Optional. If set to true deletion of the instance will fail. "

mmv1/products/redis/Cluster.yaml

Lines changed: 0 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -378,14 +378,6 @@ properties:
378378
type: String
379379
description: |
380380
Immutable. The zone for single zone Memorystore Redis cluster.
381-
- name: 'allowFewerZonesDeployment'
382-
type: Boolean
383-
immutable: true
384-
description: |
385-
Allows customers to specify if they are okay with deploying a multi-zone
386-
cluster in less than 3 zones. Once set, if there is a zonal outage during
387-
the cluster creation, the cluster will only be deployed in 2 zones, and
388-
stay within the 2 zones for its lifecycle.
389381
- name: 'pscConfigs'
390382
type: Array
391383
description: |

mmv1/templates/terraform/examples/memorystore_instance_full.tf.tmpl

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,6 @@ resource "google_memorystore_instance" "{{$.PrimaryResourceId}}" {
1414
engine_configs = {
1515
maxmemory-policy = "volatile-ttl"
1616
}
17-
allow_fewer_zones_deployment = true
1817
zone_distribution_config {
1918
mode = "SINGLE_ZONE"
2019
zone = "us-central1-b"

mmv1/templates/terraform/examples/redis_cluster_aof.tf.tmpl

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,6 @@ resource "google_redis_cluster" "{{$.PrimaryResourceId}}" {
1313
maxmemory-policy = "volatile-ttl"
1414
}
1515
deletion_protection_enabled = {{index $.Vars "deletion_protection_enabled"}}
16-
allow_fewer_zones_deployment = true
1716
zone_distribution_config {
1817
mode = "MULTI_ZONE"
1918
}

mmv1/third_party/terraform/website/docs/guides/version_7_upgrade.html.markdown

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -268,3 +268,11 @@ Remove `template.containers.depends_on` from your configuration after upgrade.
268268
The default value for `disable_on_destroy` has been changed to `false`. The previous default (`true`) created a risk of unintended service disruptions, as destroying a single `google_project_service` resource would disable the API for the entire project.
269269

270270
Now, destroying the resource will only remove it from Terraform's state and leave the service enabled. To disable a service when the resource is destroyed, you must now make an explicit decision by setting `disable_on_destroy = true`.
271+
272+
## Resource: `google_memorystore_instance`
273+
274+
`allow_fewer_zones_deployment` has been removed because it isn't user-configurable.
275+
276+
## Resource: `google_redis_cluster`
277+
278+
`allow_fewer_zones_deployment` has been removed because it isn't user-configurable.

0 commit comments

Comments
 (0)