Terraform vs Deployment Manager decision in GCP - Hands-On Comparison

Terraform vs Deployment Manager Decision

📖 Scenario: You are working as a cloud engineer for a company moving their infrastructure to Google Cloud Platform (GCP). Your team needs to decide whether to use Terraform or Google Cloud Deployment Manager to manage infrastructure as code.Both tools help automate resource creation, but they have differences in flexibility, community support, and integration.

🎯 Goal: Build a simple comparison dictionary in Python that lists key features of Terraform and Deployment Manager. Then, add a configuration variable to select the preferred tool. Finally, write logic to print the chosen tool's features.

📋 What You'll Learn

Create a dictionary named tools with keys 'Terraform' and 'Deployment Manager' and their feature descriptions as values.

Add a variable named preferred_tool set to either 'Terraform' or 'Deployment Manager'.

Write a for loop that iterates over tools.items() and prints the features of the preferred_tool.

Add a final print statement confirming the selected tool.

💡 Why This Matters

🌍 Real World

Cloud engineers often compare infrastructure as code tools to choose the best fit for their projects. Automating this comparison helps in decision making.

💼 Career

Understanding how to manage and compare cloud infrastructure tools is essential for roles like Cloud Engineer, DevOps Engineer, and Site Reliability Engineer.

1

Create the tools dictionary

Create a dictionary called tools with these exact entries: 'Terraform' mapped to 'Open-source, multi-cloud, large community' and 'Deployment Manager' mapped to 'GCP native, YAML/JSON configs, integrates with GCP services'.

GCP

# Create the tools dictionary with exact keys and values
# Your code here

Hint

Use curly braces {} to create a dictionary with the exact keys and values.

2

Add preferred tool variable

Add a variable called preferred_tool and set it to the string 'Terraform'.

GCP

tools = {
    'Terraform': 'Open-source, multi-cloud, large community',
    'Deployment Manager': 'GCP native, YAML/JSON configs, integrates with GCP services'
}
# Set preferred_tool to 'Terraform'
# Your code here

Hint

Assign the string 'Terraform' to the variable preferred_tool.

3

Write loop to print preferred tool features

Write a for loop using variables tool and features to iterate over tools.items(). Inside the loop, use an if statement to check if tool equals preferred_tool. If yes, print the string f"Features of {tool}: {features}".

GCP

tools = {
    'Terraform': 'Open-source, multi-cloud, large community',
    'Deployment Manager': 'GCP native, YAML/JSON configs, integrates with GCP services'
}
preferred_tool = 'Terraform'
# Write a for loop to print features of preferred_tool
# Your code here

Hint

Use for tool, features in tools.items(): and inside it check if tool == preferred_tool:.

4

Add final confirmation print

Add a print statement that outputs f"Selected tool: {preferred_tool}" to confirm the choice.

GCP

tools = {
    'Terraform': 'Open-source, multi-cloud, large community',
    'Deployment Manager': 'GCP native, YAML/JSON configs, integrates with GCP services'
}
preferred_tool = 'Terraform'
for tool, features in tools.items():
    if tool == preferred_tool:
        print(f"Features of {tool}: {features}")
# Add final print to confirm selected tool
# Your code here

Hint

Use a print statement with an f-string to show the selected tool.

Practice

1. Which tool is best described as Google Cloud's native infrastructure management service?

easy

A. Deployment Manager

B. Terraform

C. Ansible

D. Chef

Solution

1. Step 1: Understand native tools in GCP

   Deployment Manager is built by Google specifically for managing GCP resources.

2. Step 2: Compare with other tools

   Terraform is multi-cloud and not native to GCP, while Ansible and Chef are configuration management tools, not native GCP infrastructure managers.

3. Final Answer:

   Deployment Manager -> Option A

4. Quick Check:

   Native GCP tool = Deployment Manager [OK]

Hint: Native GCP tool means Deployment Manager [OK]

Common Mistakes:

• Confusing Terraform as native to GCP
• Mixing configuration tools with infrastructure tools
• Assuming multi-cloud tools are native

2. Which syntax snippet correctly initializes a Terraform configuration for Google Cloud?

easy

A. resource "gcp_project" { name = "my-project" }

B. provider "google" { project = "my-project" region = "us-central1" }

C. deployment "my-deployment" { config: "config.yaml" }

D. service "google" { project = "my-project" }

Solution

1. Step 1: Identify Terraform provider syntax

   Terraform uses the keyword 'provider' with the provider name and configuration inside curly braces.

2. Step 2: Check other options

   resource "gcp_project" { name = "my-project" } uses incorrect resource type, C is Deployment Manager style, D uses invalid keyword 'service'.

3. Final Answer:

   provider "google" { project = "my-project" region = "us-central1" } -> Option B

4. Quick Check:

   Terraform provider block = provider "google" { project = "my-project" region = "us-central1" } [OK]

Hint: Terraform uses 'provider' block for cloud setup [OK]

Common Mistakes:

• Confusing Deployment Manager syntax with Terraform
• Using wrong keywords like 'service' instead of 'provider'
• Incorrect resource types for Terraform

3. Given this Terraform snippet:

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

What will happen when you run terraform apply?

medium

A. A new VM instance named 'test-vm' will be created in us-central1-a zone.

B. Terraform will throw a syntax error due to missing provider block.

C. The VM will be created but without a boot disk.

D. Terraform will delete all existing instances in the default network.

Solution

1. Step 1: Analyze resource block

   The resource defines a Google Compute VM named 'test-vm' with specified machine type, zone, boot disk image, and network interface.

2. Step 2: Understand Terraform apply behavior

   Terraform will create the VM as described if the provider is configured elsewhere; missing provider block causes error only if not configured.

3. Final Answer:

   A new VM instance named 'test-vm' will be created in us-central1-a zone. -> Option A

4. Quick Check:

   Terraform creates resources as defined [OK]

Hint: Terraform creates resources exactly as defined [OK]

Common Mistakes:

• Assuming missing provider block always causes error
• Thinking boot disk is optional and missing
• Believing Terraform deletes unrelated resources

4. You wrote a Deployment Manager config but get an error: Invalid resource type. What is the most likely cause?

medium

A. Missing project ID in the config file

B. Not enabling the Compute Engine API

C. Incorrect indentation in YAML file

D. Using a Terraform resource type in Deployment Manager config

Solution

1. Step 1: Understand resource types in Deployment Manager

   Deployment Manager requires resource types specific to GCP and its own syntax, not Terraform resource types.

2. Step 2: Identify error cause

   Using Terraform resource types in Deployment Manager config causes 'Invalid resource type' error.

3. Final Answer:

   Using a Terraform resource type in Deployment Manager config -> Option D

4. Quick Check:

   Resource types must match tool syntax [OK]

Hint: Use correct resource types per tool [OK]

Common Mistakes:

• Confusing Terraform and Deployment Manager resource types
• Ignoring API enablement errors
• Assuming YAML indentation causes resource type errors

5. Your team needs to manage infrastructure across multiple clouds with a single tool and prefers simple, readable syntax. Which tool should you choose?

hard

A. Deployment Manager because it is native to GCP

B. Use Deployment Manager with custom scripts for multi-cloud

C. Terraform because it supports multiple clouds and has simple syntax

D. Manual scripting with gcloud CLI for flexibility

Solution

1. Step 1: Analyze multi-cloud support

   Deployment Manager only supports GCP, so it cannot manage multiple clouds.

2. Step 2: Consider syntax and team preference

   Terraform supports multiple clouds and uses simple, readable syntax, fitting team needs.

3. Step 3: Evaluate other options

   Manual scripting is error-prone and less maintainable; Deployment Manager with scripts is complex and limited to GCP.

4. Final Answer:

   Terraform because it supports multiple clouds and has simple syntax -> Option C

5. Quick Check:

   Multi-cloud + simple syntax = Terraform [OK]

Hint: Multi-cloud needs point to Terraform [OK]

Common Mistakes:

• Choosing Deployment Manager for multi-cloud
• Thinking manual scripts are simpler
• Assuming Deployment Manager can be extended easily for other clouds