fixes after CR: default services_secondary_range_name to null.

gruntwork-io · Mar 31, 2020 · 89e4f93 · 89e4f93
1 parent 95a33a5
commit 89e4f93
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/modules/gke-cluster/main.tf b/modules/gke-cluster/main.tf
@@ -64,7 +64,7 @@ resource "google_container_cluster" "cluster" {
   ip_allocation_policy {
     // Choose the range, but let GCP pick the IPs within the range
     cluster_secondary_range_name  = var.cluster_secondary_range_name
-    services_secondary_range_name = var.services_secondary_range_name != "" ? var.services_secondary_range_name : var.cluster_secondary_range_name
+    services_secondary_range_name = var.services_secondary_range_name != null ? var.services_secondary_range_name : var.cluster_secondary_range_name
   }
 
   # We can optionally control access to the cluster

diff --git a/modules/gke-cluster/variables.tf b/modules/gke-cluster/variables.tf
@@ -207,5 +207,5 @@ variable "enable_vertical_pod_autoscaling" {
 variable "services_secondary_range_name" {
   description = "The name of the secondary range within the subnetwork for the services to use"
   type        = string
-  default     = ""
+  default     = null
 }