Terraform GCP provider setup - Mini Project: Build & Apply

Terraform GCP provider setup

📖 Scenario: You are starting a new cloud project on Google Cloud Platform (GCP). To manage your cloud resources efficiently, you want to use Terraform, a tool that helps you write code to create and manage cloud infrastructure.Before you can create any resources, you need to set up Terraform to connect to your GCP account properly.

🎯 Goal: Set up Terraform configuration to use the GCP provider with the correct project and region settings.

📋 What You'll Learn

Create a Terraform configuration file named main.tf.

Configure the GCP provider with the exact project ID my-gcp-project-123.

Set the region to us-central1.

Specify the provider version as 4.0.0.

Add a variable for the project ID with a default value.

💡 Why This Matters

🌍 Real World

Terraform is widely used to manage cloud infrastructure as code. Setting up the provider correctly is the first step to automate resource creation and management on GCP.

💼 Career

Cloud engineers and DevOps professionals must know how to configure Terraform providers to work with cloud platforms like GCP for efficient infrastructure automation.

1

Create Terraform configuration file with provider block

Create a file named main.tf and write a terraform block with required providers specifying google = { source = "hashicorp/google", version = "4.0.0" }. Then add a provider block for google with project = "my-gcp-project-123" and region = "us-central1".

GCP

# Your code here to create terraform and provider blocks

Hint

Start by defining the terraform block with required_providers. Then add the provider "google" block with the project and region.

2

Add a variable for the project ID

Add a Terraform variable block named project_id with a default value set to "my-gcp-project-123".

GCP

terraform {
  required_providers {
    google = {
      source  = "hashicorp/google"
      version = "4.0.0"
    }
  }
}

provider "google" {
  project = "my-gcp-project-123"
  region  = "us-central1"
}

# Your code here to add variable block

Hint

Use the variable keyword followed by the variable name and set the default value inside curly braces.

3

Use the variable in the provider block

Modify the provider "google" block to use the variable project_id for the project attribute by setting project = var.project_id.

GCP

terraform {
  required_providers {
    google = {
      source  = "hashicorp/google"
      version = "4.0.0"
    }
  }
}

provider "google" {
  project = "my-gcp-project-123"
  region  = "us-central1"
}

variable "project_id" {
  default = "my-gcp-project-123"
}

# Your code here to update provider project to use var.project_id

Hint

Replace the fixed project string with var.project_id inside the provider block.

4

Add a backend configuration for remote state

Add a terraform backend block inside the existing terraform block to configure remote state storage using gcs with bucket = "my-terraform-state-bucket" and prefix = "terraform/state".

GCP

terraform {
  required_providers {
    google = {
      source  = "hashicorp/google"
      version = "4.0.0"
    }
  }

  # Your code here to add backend block
}

provider "google" {
  project = var.project_id
  region  = "us-central1"
}

variable "project_id" {
  default = "my-gcp-project-123"
}

Hint

Inside the terraform block, add a backend "gcs" block with the bucket and prefix settings.

Practice

1. What is the main purpose of the provider block in a Terraform configuration for GCP?

easy

A. To store user credentials permanently

B. To define virtual machines in GCP

C. To create network firewalls automatically

D. To connect Terraform to Google Cloud services

Solution

1. Step 1: Understand the role of the provider block

   The provider block tells Terraform which cloud service to use and how to connect to it.

2. Step 2: Identify the specific function for GCP

   For Google Cloud, the provider block sets up the connection using project ID, region, and credentials.

3. Final Answer:

   To connect Terraform to Google Cloud services -> Option D

4. Quick Check:

   Provider block = Connect Terraform to cloud [OK]

Hint: Provider block always sets up cloud connection [OK]

Common Mistakes:

• Confusing provider block with resource definitions
• Thinking provider stores credentials permanently
• Assuming provider creates resources automatically

2. Which of the following is the correct syntax to specify the GCP project ID in the Terraform provider block?

easy

A. project = "my-gcp-project"

B. project_id = "my-gcp-project"

C. gcp_project = "my-gcp-project"

D. id_project = "my-gcp-project"

Solution

1. Step 1: Recall the correct attribute name for project ID

   In Terraform's GCP provider, the attribute to set the project is project.

2. Step 2: Match the correct syntax

   The correct syntax is project = "my-gcp-project", which matches project = "my-gcp-project".

3. Final Answer:

   project = "my-gcp-project" -> Option A

4. Quick Check:

   Project ID attribute = project [OK]

Hint: Use 'project' keyword for project ID in provider [OK]

Common Mistakes:

• Using project_id instead of project
• Mixing attribute names like gcp_project
• Misspelling the attribute name

3. Given this Terraform provider block snippet:

provider "google" {
  project = var.project_id
  region  = "us-central1"
  credentials = file("account.json")
}

What will happen if the file account.json is missing or unreadable?

medium

A. Terraform will throw an error and stop

B. Terraform will apply changes without authentication

C. Terraform will use default credentials automatically

D. Terraform will ignore the credentials and proceed

Solution

1. Step 1: Understand the role of credentials in provider block

   The credentials file provides authentication details needed to access GCP.

2. Step 2: Identify behavior when credentials file is missing

   If the file is missing or unreadable, Terraform cannot authenticate and will throw an error, stopping the process.

3. Final Answer:

   Terraform will throw an error and stop -> Option A

4. Quick Check:

   Missing credentials file = error stop [OK]

Hint: Missing credentials file causes error [OK]

Common Mistakes:

• Assuming Terraform skips authentication
• Thinking default credentials always apply
• Believing Terraform proceeds without credentials

4. You wrote this provider block:

provider "google" {
  project = var.project
  region = var.region
  credentials = file("credentials.json")
}

Terraform gives an error: <code>"var.project" is not defined.
What is the likely cause and fix?

medium

A. The provider block must not use variables; replace with fixed strings

B. The file credentials.json is missing; add the file

C. Variables project and region are not declared; declare them in variables.tf

D. Terraform does not support variable use in provider blocks; remove variables

Solution

1. Step 1: Analyze the error message

   The error says var.project is not defined, meaning Terraform cannot find the variable declaration.

2. Step 2: Understand variable usage in Terraform

   Variables must be declared in a variables.tf file or equivalent before use.

3. Final Answer:

   Variables project and region are not declared; declare them in variables.tf -> Option C

4. Quick Check:

   Undefined variable error = declare variables [OK]

Hint: Declare variables before using them in provider [OK]

Common Mistakes:

• Assuming missing credentials file causes this error
• Thinking variables can't be used in provider block
• Ignoring the need to declare variables explicitly

5. You want to set up the Terraform GCP provider to use different projects and regions without changing code. Which is the best practice to achieve this?

hard

A. Hardcode project and region in the provider block

B. Use variables for project and region and pass values at runtime

C. Create multiple provider blocks with fixed values for each environment

D. Store credentials inside the Terraform code directly

Solution

1. Step 1: Understand flexibility needs

   To switch projects and regions easily, avoid hardcoding values in code.

2. Step 2: Use variables for dynamic configuration

   Using variables allows passing different values at runtime without changing code, which is best practice.

3. Step 3: Avoid insecure or rigid methods

   Hardcoding or multiple fixed provider blocks reduce flexibility; storing credentials in code risks security.

4. Final Answer:

   Use variables for project and region and pass values at runtime -> Option B

5. Quick Check:

   Variables for flexibility = best practice [OK]

Hint: Use variables to change project and region easily [OK]

Common Mistakes:

• Hardcoding values reduces flexibility
• Duplicating provider blocks causes maintenance issues
• Embedding credentials in code risks security