Editing article

Title

Summary

Content

<h3>Build Infrastructure on Google Cloud with Terraform — Google Challenge Lab Walkthrough</h3>This is a walkthrough of the <a href="https://partner.cloudskillsboost.google/focuses/16515?parent=catalog">challenge lab</a> from the course <a href="https://www.cloudskillsboost.google/course_templates/636">Build Infrastructure with Terraform on Google Cloud</a>.This lab tests your ability to:<ul><li>Import existing infrastructure into your Terraform configuration.</li><li>Build and reference your own Terraform modules.</li><li>Add a remote backend to your configuration.</li><li>Use and implement a module from the Terraform Registry.</li><li>Re-provision, destroy, and update infrastructure.</li><li>Test connectivity between the resources you’ve created.</li></ul><h3>Intro to Challenge Labs</h3>Google provides an online learning platform called Google <a href="https://www.cloudskillsboost.google/">Cloud Skills Boost</a>, formerly known as QwikLabs. On this platform, you can follow training courses aligned to learning paths, to particular products, or for particular solutions.One type of learning experience on this platform is called a quest. This is where you complete a number of guided hands-on labs, and then finally complete a Challenge Lab. The challenge lab differs from the other labs in that goals are specified, but very little guidance on how to achieve the goals is given.I occasionally create walkthroughs of these challenge labs. The goal is not to help you cheat your way through the challenge labs! But rather:<ul><li>To show you what I believe to be an ideal route through the lab.</li><li>To help you with particular gotchas or blockers that are preventing you from completing the lab on your own.</li></ul>If you’re looking for help with challenge lab, then you’ve come to the right place. But I strongly urge you to work your way through the quest first, and to try the lab on your own, before reading further!With all these labs, there are always many ways to go about solving the problem. I generally like to solve them using the Cloud Shell, since I can then document a more repeatable and programmatic approach. But of course, you can use the Cloud Console too.<h3>Overview of this Lab</h3>In this lab we’re expected to use Terraform to create, deploy and manage infrastructure on Google Cloud. We also need to import some mismanaged instances into our configuration and fix them.<h3>My Solution</h3>Let’s start by defining some variables we can use throughout this challenge. The actual variables will be provided to you when you start the lab.<pre>gcloud auth list region=&lt;ENTER REGION&gt; zone=&lt;ENTER ZONE&gt; prj=&lt;ENTER PRJ ID&gt;</pre><h4>Task 1 — Create the Configuration Files</h4>We’re told to create this folder structure:<pre>main.tf variables.tf modules/ └── instances | ├── instances.tf | ├── outputs.tf | └── variables.tf └── storage ├── storage.tf ├── outputs.tf └── variables.tf</pre>We can do it like this:<pre># Create main.tf and variables.tf in the root directory touch main.tf variables.tf # Create main directory and its files mkdir -p modules/instances mkdir modules/storage # Create the required files in the &#39;instances&#39; module directory touch modules/instances/instances.tf touch modules/instances/outputs.tf touch modules/instances/variables.tf # Create the required files in the &#39;storage&#39; module directory touch modules/storage/storage.tf touch modules/storage/outputs.tf touch modules/storage/variables.tf</pre>Now we update the variables.tf files to contain these variables:<pre>variable &quot;region&quot; { description = &quot;The Google Cloud region&quot; type = string default = &quot;Lab-supplied region&quot; } variable &quot;zone&quot; { description = &quot;The Google Cloud zone&quot; type = string default = &quot;Lab-supplied zone&quot; } variable &quot;project_id&quot; { description = &quot;The ID of the project in which to provision resources.&quot; type = string default = &quot;Your project ID&quot; }</pre>Update the root module main.tf to include the Google Cloud Provider, which you can always look up in the <a href="https://registry.terraform.io/providers/hashicorp/google/latest/docs">Terraform Registry</a>. We’re asked to include all three of our variables in our provider block.<pre>terraform { required_providers { google = { source = &quot;hashicorp/google&quot; } } } provider &quot;google&quot; { project = var.project_id region = var.region zone = var.zone }</pre>Now we need to initialise Terraform. So run this command:<pre>terraform init</pre><h4>Task 2 — Import Infrastructure</h4>Here, the goal is to bring infrastructure under Terraform control, that has thus far been provisioned outside of Terraform.We’re going to use the Terraform import workflow:<figure><img alt="" src="https://cdn-images-1.medium.com/max/737/0*cLTWjcD7L2rsBcRO.png" /><figcaption>Terraform import workflow</figcaption></figure>These are the import steps:<ol><li>Identify the existing infrastructure to be imported.</li><li>Import the infrastructure into your Terraform state.</li><li>Write a Terraform configuration that matches that infrastructure.</li><li>Review the Terraform plan to ensure that the configuration matches the expected state and infrastructure.</li><li>Apply the configuration to update your Terraform state.</li></ol><h4>Identify the existing infrastructure to be imported</h4>Two GCE instances have already been created. Examine one of the existing instances, tf-instance-1 in the Cloud Console. We want to retrieve:<ul><li>Network</li><li>Machine type</li><li>Disk</li></ul>Next we need to include two calls to our instances module in our main.tf. They will contain empty definitions, so that we can import.<pre>module &quot;tf_instance_1&quot; { source = &quot;./modules/instances&quot; instance_name = &quot;tf-instance-1&quot; zone = var.zone region = var.region } module &quot;tf_instance_2&quot; { source = &quot;./modules/instances&quot; instance_name = &quot;tf-instance-2&quot; zone = var.zone region = var.region }</pre>Remember that each module definition must have a unique label.Now initialise:<pre>terraform init</pre>Now we write the <a href="https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/compute_instance">module configurations</a> in instances.tf. We’re told the arguments that need to be included in our minimal configuration:<pre>resource &quot;google_compute_instance&quot; &quot;instance&quot; { name = var.instance_name machine_type = &quot;hard code from existing instance&quot; zone = var.zone boot_disk { initialize_params { # image = &quot;debian-cloud/debian-11&quot; image = &quot;hard code from existing instance&quot; } } network_interface { # network = &quot;default&quot; network = &quot;hard code from existing instance&quot; access_config { // Ephemeral public IP } } metadata_startup_script = &lt;&lt;-EOT #!/bin/bash EOT allow_stopping_for_update = true }</pre>Update variables.tf in the instance module, so we can pass in the instance_name:<pre>variable &quot;instance_name&quot; { description = &quot;The name of the instance.&quot; type = string }</pre><h4>Import the Existing Infrastructure into Terraform State</h4><pre>terraform import module.tf_instance_1.google_compute_instance.instance \ projects/$prj/zones/$zone/instances/tf-instance-1 terraform import module.tf_instance_2.google_compute_instance.instance \ projects/$prj/zones/$zone/instances/tf-instance-2 # verify the import terraform show</pre>The import should look like this:<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*1YafhrvtKcZG7MrQ.png" /><figcaption>terraform import</figcaption></figure><h4>Plan and Apply</h4>Now we update the instances in-place by running the apply:<pre>terraform plan terraform apply</pre><h4>Task 3 — Configure a Remote Backend</h4>This is pretty easy. These are standard steps that you would run whenever we want to store Terraform state in a remote GCS backend:<ol><li>Provision a GCS bucket with Terraform.</li><li>Add a backend block that points to the new GCS bucket.</li><li>Reinitialise Terraform and migrate the state from the local state file to the remote backend.</li></ol><h4>Provision the GCS Bucket</h4>Add this resource definition to main.tf:<pre>resource &quot;google_storage_bucket&quot; &quot;test-bucket-for-state&quot; { name = &quot;Bucket Name You Are Given&quot; location = &quot;US&quot; uniform_bucket_level_access = true force_destroy = true }</pre>And apply:<pre>terraform apply</pre><h4>Add the GCS Backend</h4>Modify main.tf and include the backend in the terraform block:<pre>terraform { backend &quot;gcs&quot; { bucket = var.project_id prefix = &quot;terraform/state&quot; } }</pre><h4>Migrate the State</h4>This is where we migrate the Terraform state from the local state file into the GCS backend:<pre>terraform init -migrate-state</pre>It will ask you to confirm you want to migrate the state:<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*qJ3EoohrCM8M5h7V.png" /><figcaption>Migrating Terraform state</figcaption></figure><h4>Task 4 — Modify and Update the Infrastructure</h4>We need to update variables.tf to include a machine_type:<pre>variable &quot;machine_type&quot; { description = &quot;The machine type of an instance&quot; type = string default = &quot;e2-standard-2&quot; }</pre>Then we need to modify instance.tf so that it can accept a machine_type parameter:<pre>resource &quot;google_compute_instance&quot; &quot;instance&quot; { name = var.instance_name machine_type = var.machine_type zone = var.zone ...</pre>Lastly, we need to modify main.tf such that we add the specified third instance to our main.tf, by calling the module for a third time. We don’t need to pass in the machine_type, as we’ve already set it to have a default.Now initialise (because we’ve added another module instance) and apply.<pre>terraform init terraform apply</pre><h4>Task 5 — Destroy Resources</h4>Now we remove the instance we previously added. Remove the call to this module from main.tf, then reapply:<pre>terraform init terraform apply</pre><h4>Task 6 — Use a Module from the Registry</h4>We’re going to use the <a href="https://registry.terraform.io/modules/terraform-google-modules/network/google/6.0.0">Google Network Module</a>.<pre>module &quot;network&quot; { source = &quot;terraform-google-modules/network/google&quot; version = &quot;6.0.0&quot; project_id = var.project_id network_name = &quot;Use Supplied VPC Name&quot; routing_mode = &quot;GLOBAL&quot; subnets = [ { subnet_name = &quot;subnet-01&quot; subnet_ip = &quot;10.10.10.0/24&quot; subnet_region = var.region }, { subnet_name = &quot;subnet-02&quot; subnet_ip = &quot;10.10.20.0/24&quot; subnet_region = var.region } ] }</pre>Initialise and apply:<pre>terraform init terraform apply</pre>Update instances module to take a network parameter and a subnet parameter.In variables.tf:<pre>variable &quot;network&quot; { description = &quot;The network&quot; type = string } variable &quot;subnet&quot; { description = &quot;The subnet&quot; type = string }</pre>In instance.tf:<pre>network_interface { network = var.network subnetwork = var.subnet access_config { // Ephemeral public IP } }</pre>Then update main.tf to create the instances like this:<pre>module &quot;tf_instance_1&quot; { source = &quot;./modules/instances&quot; instance_name = &quot;tf-instance-1&quot; zone = var.zone region = var.region network = module.network.network_name subnet = &quot;subnet-01&quot; } module &quot;tf_instance_2&quot; { source = &quot;./modules/instances&quot; instance_name = &quot;tf-instance-2&quot; zone = var.zone region = var.region network = module.network.network_name subnet = &quot;subnet-02&quot; }</pre><pre>terraform init terraform apply</pre><h4>Task 7 — Add a Firewall</h4>Update main.tf:<pre>resource &quot;google_compute_firewall&quot; &quot;default&quot; { name = &quot;tf-firewall&quot; network = module.network.network_name direction = &quot;INGRESS&quot; source_ranges = [&quot;0.0.0.0/0&quot;] allow { protocol = &quot;tcp&quot; ports = [&quot;80&quot;] } }</pre>And one last apply…<pre>terraform apply</pre>And we’re done!<img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=30a592373d3e" width="1" height="1" alt=""><hr><a href="https://medium.com/google-cloud/build-infrastructure-on-google-cloud-with-terraform-google-challenge-lab-walkthrough-30a592373d3e">Build Infrastructure on Google Cloud with Terraform — Google Challenge Lab Walkthrough</a> was originally published in <a href="https://medium.com/google-cloud">Google Cloud - Community</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.

Author

Link

Published date

Image url

Feed url

Guid

Hidden blurb

--- !ruby/object:Feedjira::Parser::RSSEntry
title: Build Infrastructure on Google Cloud with Terraform — Google Challenge Lab
 Walkthrough
published: 2024-04-05 04:49:54.000000000 Z
categories:
- challenge-lab
- google-cloud-platform
- terraform
- infrastructure
- terraform-import
entry_id: !ruby/object:Feedjira::Parser::GloballyUniqueIdentifier
 is_perma_link: 'false'
 guid: https://medium.com/p/30a592373d3e
carlessian_info:
 news_filer_version: 2
 newspaper: Google Cloud - Medium
 macro_region: Blogs
content: '<h3>Build Infrastructure on Google Cloud with Terraform — Google Challenge
 Lab Walkthrough</h3>This is a walkthrough of the <a href="https://partner.cloudskillsboost.google/focuses/16515?parent=catalog">challenge
 lab</a> from the course <a href="https://www.cloudskillsboost.google/course_templates/636">Build
 Infrastructure with Terraform on Google Cloud</a>.This lab tests your ability to:<ul><li>Import
 existing infrastructure into your Terraform configuration.</li><li>Build and reference
 your own Terraform modules.</li><li>Add a remote backend to your configuration.</li><li>Use
 and implement a module from the Terraform Registry.</li><li>Re-provision, destroy,
 and update infrastructure.</li><li>Test connectivity between the resources you’ve created.</li></ul><h3>Intro
 to Challenge Labs</h3>Google provides an online learning platform called Google
 <a href="https://www.cloudskillsboost.google/">Cloud Skills Boost</a>, formerly
 known as QwikLabs. On this platform, you can follow training courses aligned to
 learning paths, to particular products, or for particular solutions.One type
 of learning experience on this platform is called a quest. This
 is where you complete a number of guided hands-on labs, and then finally complete
 a Challenge Lab. The challenge lab differs from
 the other labs in that goals are specified, but very little guidance on how
 to achieve the goals is given.I occasionally create walkthroughs of these
 challenge labs. The goal is not to help you cheat your way through the challenge
 labs! But rather:<ul><li>To show you what I believe to be an ideal route through
 the lab.</li><li>To help you with particular gotchas or blockers that are preventing
 you from completing the lab on your own.</li></ul>If you’re looking for help
 with challenge lab, then you’ve come to the right place. But I strongly urge you
 to work your way through the quest first, and to try the lab on your own, before
 reading further!With all these labs, there are always many ways to go about
 solving the problem. I generally like to solve them using the Cloud Shell, since
 I can then document a more repeatable and programmatic approach. But of course,
 you can use the Cloud Console too.<h3>Overview of this Lab</h3>In this lab
 we’re expected to use Terraform to create, deploy and manage infrastructure on Google
 Cloud. We also need to import some mismanaged instances into our configuration and
 fix them.<h3>My Solution</h3>Let’s start by defining some variables we can
 use throughout this challenge. The actual variables will be provided to you when
 you start the lab.<pre>gcloud auth list region=&lt;ENTER REGION&gt; zone=&lt;ENTER
 ZONE&gt; prj=&lt;ENTER PRJ ID&gt;</pre><h4>Task 1 — Create the Configuration
 Files</h4>We’re told to create this folder structure:<pre>main.tf variables.tf modules/ └──
 instances | ├── instances.tf | ├── outputs.tf | └── variables.tf └──
 storage ├── storage.tf ├── outputs.tf └── variables.tf</pre>We
 can do it like this:<pre># Create main.tf and variables.tf in the root directory touch
 main.tf variables.tf # Create main directory and its files mkdir -p modules/instances mkdir
 modules/storage # Create the required files in the &#39;instances&#39; module
 directory touch modules/instances/instances.tf touch modules/instances/outputs.tf touch
 modules/instances/variables.tf # Create the required files in the &#39;storage&#39;
 module directory touch modules/storage/storage.tf touch modules/storage/outputs.tf touch
 modules/storage/variables.tf</pre>Now we update the variables.tf files to contain
 these variables:<pre>variable &quot;region&quot; { description = &quot;The
 Google Cloud region&quot; type = string default = &quot;Lab-supplied
 region&quot; } variable &quot;zone&quot; { description = &quot;The
 Google Cloud zone&quot; type = string default = &quot;Lab-supplied
 zone&quot; } variable &quot;project_id&quot; { description = &quot;The
 ID of the project in which to provision resources.&quot; type = string default =
 &quot;Your project ID&quot; }</pre>Update the root module main.tf to include
 the Google Cloud Provider, which you can always look up in the <a href="https://registry.terraform.io/providers/hashicorp/google/latest/docs">Terraform
 Registry</a>. We’re asked to include all three of our variables in our provider block.<pre>terraform
 { required_providers { google = { source = &quot;hashicorp/google&quot; } } } provider
 &quot;google&quot; { project = var.project_id region = var.region zone =
 var.zone }</pre>Now we need to initialise Terraform. So run this command:<pre>terraform
 init</pre><h4>Task 2 — Import Infrastructure</h4>Here, the goal is to bring infrastructure
 under Terraform control, that has thus far been provisioned outside of Terraform.We’re
 going to use the Terraform import workflow:<figure><img alt="" src="https://cdn-images-1.medium.com/max/737/0*cLTWjcD7L2rsBcRO.png"
 /><figcaption>Terraform import workflow</figcaption></figure>These are the import steps:<ol><li>Identify
 the existing infrastructure to be imported.</li><li>Import the infrastructure into
 your Terraform state.</li><li>Write a Terraform configuration
 that matches that infrastructure.</li><li>Review the Terraform plan
 to ensure that the configuration matches the expected state and infrastructure.</li><li>Apply
 the configuration to update your Terraform state.</li></ol><h4>Identify
 the existing infrastructure to be imported</h4>Two GCE instances have already
 been created. Examine one of the existing instances, tf-instance-1 in the Cloud
 Console. We want to retrieve:<ul><li>Network</li><li>Machine type</li><li>Disk</li></ul>Next
 we need to include two calls to our instances module in our main.tf. They will contain
 empty definitions, so that we can import.<pre>module &quot;tf_instance_1&quot;
 { source = &quot;./modules/instances&quot; instance_name = &quot;tf-instance-1&quot; zone =
 var.zone region = var.region } module &quot;tf_instance_2&quot;
 { source = &quot;./modules/instances&quot; instance_name = &quot;tf-instance-2&quot; zone =
 var.zone region = var.region }</pre>Remember that each module
 definition must have a unique label.Now initialise:<pre>terraform init</pre>Now
 we write the <a href="https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/compute_instance">module
 configurations</a> in instances.tf. We’re told the arguments that need to be included
 in our minimal configuration:<pre>resource &quot;google_compute_instance&quot;
 &quot;instance&quot; { name = var.instance_name machine_type =
 &quot;hard code from existing instance&quot; zone = var.zone boot_disk
 { initialize_params { # image = &quot;debian-cloud/debian-11&quot; image
 = &quot;hard code from existing instance&quot; } } network_interface
 { # network = &quot;default&quot; network = &quot;hard code from existing
 instance&quot; access_config { // Ephemeral public IP } } metadata_startup_script
 = &lt;&lt;-EOT #!/bin/bash EOT allow_stopping_for_update
 = true }</pre>Update variables.tf in the instance module, so we can pass in
 the instance_name:<pre>variable &quot;instance_name&quot; { description
 = &quot;The name of the instance.&quot; type = string }</pre><h4>Import
 the Existing Infrastructure into Terraform State</h4><pre>terraform import module.tf_instance_1.google_compute_instance.instance
 \ projects/$prj/zones/$zone/instances/tf-instance-1 terraform import
 module.tf_instance_2.google_compute_instance.instance \ projects/$prj/zones/$zone/instances/tf-instance-2 #
 verify the import terraform show</pre>The import should look like this:<figure><img
 alt="" src="https://cdn-images-1.medium.com/max/1024/0*1YafhrvtKcZG7MrQ.png" /><figcaption>terraform
 import</figcaption></figure><h4>Plan and Apply</h4>Now we update the instances
 in-place by running the apply:<pre>terraform plan terraform apply</pre><h4>Task
 3 — Configure a Remote Backend</h4>This is pretty easy. These are standard steps
 that you would run whenever we want to store Terraform state in a remote GCS backend:<ol><li>Provision
 a GCS bucket with Terraform.</li><li>Add a backend block that points to the new
 GCS bucket.</li><li>Reinitialise Terraform and migrate the state from the local
 state file to the remote backend.</li></ol><h4>Provision the GCS Bucket</h4>Add
 this resource definition to main.tf:<pre>resource &quot;google_storage_bucket&quot;
 &quot;test-bucket-for-state&quot; { name = &quot;Bucket Name You Are
 Given&quot; location = &quot;US&quot; uniform_bucket_level_access =
 true force_destroy = true }</pre>And apply:<pre>terraform apply</pre><h4>Add
 the GCS Backend</h4>Modify main.tf and include the backend in the terraform block:<pre>terraform
 { backend &quot;gcs&quot; { bucket = var.project_id prefix =
 &quot;terraform/state&quot; } }</pre><h4>Migrate the State</h4>This is
 where we migrate the Terraform state from the local state file into the GCS backend:<pre>terraform
 init -migrate-state</pre>It will ask you to confirm you want to migrate the state:<figure><img
 alt="" src="https://cdn-images-1.medium.com/max/1024/0*qJ3EoohrCM8M5h7V.png" /><figcaption>Migrating
 Terraform state</figcaption></figure><h4>Task 4 — Modify and Update the Infrastructure</h4>We
 need to update variables.tf to include a machine_type:<pre>variable &quot;machine_type&quot;
 { description = &quot;The machine type of an instance&quot; type =
 string default = &quot;e2-standard-2&quot; }</pre>Then we need to
 modify instance.tf so that it can accept a machine_type parameter:<pre>resource
 &quot;google_compute_instance&quot; &quot;instance&quot; { name = var.instance_name machine_type
 = var.machine_type zone = var.zone ...</pre>Lastly, we
 need to modify main.tf such that we add the specified third instance to our main.tf,
 by calling the module for a third time. We don’t need to pass in the machine_type,
 as we’ve already set it to have a default.Now initialise (because we’ve added
 another module instance) and apply.<pre>terraform init terraform apply</pre><h4>Task
 5 — Destroy Resources</h4>Now we remove the instance we previously added. Remove
 the call to this module from main.tf, then reapply:<pre>terraform init terraform
 apply</pre><h4>Task 6 — Use a Module from the Registry</h4>We’re going to use
 the <a href="https://registry.terraform.io/modules/terraform-google-modules/network/google/6.0.0">Google
 Network Module</a>.<pre>module &quot;network&quot; { source = &quot;terraform-google-modules/network/google&quot; version
 = &quot;6.0.0&quot; project_id = var.project_id network_name = &quot;Use
 Supplied VPC Name&quot; routing_mode = &quot;GLOBAL&quot; subnets
 = [ { subnet_name = &quot;subnet-01&quot; subnet_ip =
 &quot;10.10.10.0/24&quot; subnet_region = var.region }, { subnet_name =
 &quot;subnet-02&quot; subnet_ip = &quot;10.10.20.0/24&quot; subnet_region =
 var.region } ] }</pre>Initialise and apply:<pre>terraform
 init terraform apply</pre>Update instances module to take a network parameter
 and a subnet parameter.In variables.tf:<pre>variable &quot;network&quot;
 { description = &quot;The network&quot; type = string } variable
 &quot;subnet&quot; { description = &quot;The subnet&quot; type =
 string }</pre>In instance.tf:<pre>network_interface { network = var.network subnetwork
 = var.subnet access_config { // Ephemeral public IP } }</pre>Then
 update main.tf to create the instances like this:<pre>module &quot;tf_instance_1&quot;
 { source = &quot;./modules/instances&quot; instance_name = &quot;tf-instance-1&quot; zone =
 var.zone region = var.region network = module.network.network_name subnet =
 &quot;subnet-01&quot; } module &quot;tf_instance_2&quot; { source =
 &quot;./modules/instances&quot; instance_name = &quot;tf-instance-2&quot; zone =
 var.zone region = var.region network = module.network.network_name subnet =
 &quot;subnet-02&quot; }</pre><pre>terraform init terraform apply</pre><h4>Task
 7 — Add a Firewall</h4>Update main.tf:<pre>resource &quot;google_compute_firewall&quot;
 &quot;default&quot; { name = &quot;tf-firewall&quot; network =
 module.network.network_name direction = &quot;INGRESS&quot; source_ranges
 = [&quot;0.0.0.0/0&quot;] allow { protocol = &quot;tcp&quot; ports =
 [&quot;80&quot;] } }</pre>And one last apply…<pre>terraform apply</pre>And
 we’re done!<img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=30a592373d3e"
 width="1" height="1" alt=""><hr><a href="https://medium.com/google-cloud/build-infrastructure-on-google-cloud-with-terraform-google-challenge-lab-walkthrough-30a592373d3e">Build
 Infrastructure on Google Cloud with Terraform — Google Challenge Lab Walkthrough</a>
 was originally published in <a href="https://medium.com/google-cloud">Google Cloud
 - Community</a> on Medium, where people are continuing the conversation by highlighting
 and responding to this story.'
rss_fields:
- title
- published
- categories
- entry_id
- content
- url
- author
url: https://medium.com/google-cloud/build-infrastructure-on-google-cloud-with-terraform-google-challenge-lab-walkthrough-30a592373d3e?source=rss----e52cf94d98af---4
author: Dazbo (Darren Lester)

Language

Active

Ricc internal notes

Ricc source

Show this article Back to articles