Why IaC matters in GCP - Visual Breakdown

Process Flow - Why IaC matters

Write Infrastructure Code

↓

Run Code to Create Resources

↓

Cloud Provider Builds Resources

↓

Resources Ready to Use

↓

Manage & Update by Changing Code

↓

Repeat: Code Controls Infrastructure

Infrastructure as Code means writing code to create and manage cloud resources automatically, making setup and updates easy and consistent.

Execution Sample

GCP

resource "google_compute_instance" "vm1" {
  name         = "vm-instance"
  machine_type = "e2-medium"
  zone         = "us-central1-a"
  boot_disk {
    initialize_params {
      image = "debian-cloud/debian-10"
    }
  }
  network_interface {
    network = "default"
    access_config {}
  }
}

This code defines a virtual machine instance in GCP that will be created automatically when applied.

Process Table

Step	Action	Code Evaluation	Result
1	Parse IaC code	Read resource block	Recognize VM instance definition
2	Send request to GCP	Create VM with name 'vm-instance'	VM creation started
3	GCP provisions VM	Allocate machine type e2-medium in zone us-central1-a	VM is created and running
4	Confirm resource state	Check VM status	VM is ready to use
5	Update code	Change machine_type to e2-standard-2	Prepare update plan
6	Apply update	Send update request to GCP	VM machine type updated
7	Verify update	Check VM machine type	VM runs with new machine type
8	End	No more changes	Infrastructure matches code

💡 All infrastructure resources are created and managed by code, ensuring consistency and easy updates.

Status Tracker

Variable	Start	After Step 2	After Step 3	After Step 6	Final
VM Instance	undefined	creation requested	running with e2-medium	updated to e2-standard-2	running with e2-standard-2

Key Moments - 2 Insights

Why do we write code instead of manually creating resources in the cloud?

Writing code lets us create and update resources automatically and consistently, as shown in execution_table steps 1 to 4, avoiding manual errors.

How does changing the code update the cloud resources?

Changing the code triggers an update plan and applies changes to the cloud, as seen in steps 5 to 7, keeping infrastructure in sync with code.

Visual Quiz - 3 Questions

Look at the execution_table at step 3, what is the state of the VM instance?

A VM is running with machine type e2-medium

B VM is stopped

C VM creation requested but not started

D VM machine type is e2-standard-2

💡 Hint

Check the 'Result' column at step 3 in execution_table.

At which step does the VM machine type get updated?

A Step 4

B Step 6

C Step 5

D Step 7

💡 Hint

Look for 'Apply update' action in execution_table.

If we skip step 5 (update code), what happens to the VM machine type?

A VM is deleted

B It changes to e2-standard-2 anyway

C It stays as e2-medium

D VM machine type becomes undefined

💡 Hint

Refer to variable_tracker and see how machine type changes only after step 5 and 6.

Concept Snapshot

IaC means writing code to create and manage cloud resources.
Run the code to build resources automatically.
Change code to update resources safely.
Keeps infrastructure consistent and repeatable.
Avoids manual setup errors and saves time.

Full Transcript

Infrastructure as Code (IaC) lets you write code to create and manage cloud resources instead of doing it manually. When you run the code, the cloud provider builds the resources for you. If you want to change something, you update the code and run it again. The cloud updates the resources to match your code. This way, your infrastructure is always consistent, easy to manage, and less error-prone.