From 2693ce0d2e996c9fbbe99d1c5b0cf367ac87d90d Mon Sep 17 00:00:00 2001
From: Vibhor Mahajan <vibhor.mahajan@gmail.com>
Date: Mon, 28 Sep 2020 18:14:19 +0530
Subject: [PATCH] Fixed Bastion health check

Currently, the bastion health check assumes that the resource will only be deployed to zone 'a'.
Related to a similar PR - https://github.com/GoogleCloudPlatform/gke-private-cluster-demo/pull/4
---
 terraform/network.tf | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/terraform/network.tf b/terraform/network.tf
index 561ab4f..903dc31 100644
--- a/terraform/network.tf
+++ b/terraform/network.tf
@@ -208,7 +208,7 @@ resource "google_compute_instance" "bastion" {
     command = <<EOF
         READY=""
         for i in $(seq 1 20); do
-          if gcloud compute ssh ${local.hostname} --project ${var.project} --zone ${var.region}-a --command uptime; then
+          if gcloud compute ssh ${local.hostname} --project ${var.project} --zone ${var.zone} --command uptime; then
             READY="yes"
             break;
           fi