GCP provider setup in Terraform - Mini Project: Build & Apply

GCP Provider Setup with Terraform

📖 Scenario: You are starting a new cloud project on Google Cloud Platform (GCP). To manage your cloud resources efficiently, you will use Terraform, a tool that helps you write code to create and manage cloud infrastructure.Before creating any resources, you need to set up the GCP provider in Terraform. This provider tells Terraform how to connect to GCP and which project and region to use.

🎯 Goal: Set up the GCP provider in Terraform with the correct project ID and region so you can start managing GCP resources using Terraform.

📋 What You'll Learn

Create a Terraform configuration file named main.tf.

Specify the terraform block with required provider version constraints.

Configure the provider block for GCP with the exact project ID my-gcp-project-123 and region us-central1.

Use the latest recommended provider version syntax.

💡 Why This Matters

🌍 Real World

Setting up the GCP provider in Terraform is the first step in automating cloud infrastructure deployment, making it easier to manage resources consistently and safely.

💼 Career

Cloud engineers and DevOps professionals use Terraform provider setup to automate infrastructure provisioning, which is a key skill for managing cloud environments efficiently.

1

Create the Terraform block with required providers

Create a terraform block that specifies the required provider google with version constraint "~> 4.0".

Terraform

# Your code here

Hint

Use the terraform block to declare required providers and their versions.

2

Add the GCP provider block with project and region

Add a provider block for google with project set to "my-gcp-project-123" and region set to "us-central1".

Terraform

terraform {
  required_providers {
    google = {
      source  = "hashicorp/google"
      version = "~> 4.0"
    }
  }
}

# Your code here

Hint

The provider block configures connection details to GCP.

3

Add a variable for the project ID

Create a variable named project_id of type string with default value "my-gcp-project-123".

Terraform

terraform {
  required_providers {
    google = {
      source  = "hashicorp/google"
      version = "~> 4.0"
    }
  }
}

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

# Your code here

Hint

Use a variable to make the project ID configurable.

4

Add a variable for the region and update provider

Create a variable named region of type string with default value "us-central1". Update the provider block to use var.region for the region.

Terraform

terraform {
  required_providers {
    google = {
      source  = "hashicorp/google"
      version = "~> 4.0"
    }
  }
}

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

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

# Your code here

Hint

Make the region configurable with a variable and update the provider accordingly.

Practice

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

easy

A. To define the virtual machine size in GCP

B. To create a new Google Cloud project automatically

C. To connect Terraform to your Google Cloud project

D. To set up billing information for Google Cloud

Solution

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

   The provider "google" block tells Terraform which cloud service to connect to and how.

2. Step 2: Identify what the provider configures

   It sets the connection details like project ID, region, and credentials to manage resources in GCP.

3. Final Answer:

   To connect Terraform to your Google Cloud project -> Option C

4. Quick Check:

   Provider block = Connect to GCP [OK]

Hint: Provider block always connects Terraform to the cloud service [OK]

Common Mistakes:

• Thinking provider creates resources directly
• Confusing provider with resource definitions
• Assuming provider sets billing or VM size

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

easy

A. project = "my-project-123"

B. project_id = "my-project-123"

C. projectName = "my-project-123"

D. projectID = "my-project-123"

Solution

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

   The official Terraform GCP provider uses project to specify the project.

2. Step 2: Check the syntax format

   The attribute is project = "my-project-123".

3. Final Answer:

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

4. Quick Check:

   Correct attribute is project [OK]

Hint: Use project [OK]

Common Mistakes:

• Using project_id instead of project
• Using camelCase like projectName or projectID
• Missing quotes around the project ID string

3. Given this Terraform provider block for GCP:

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

What will happen when you run terraform init?

medium

A. Terraform throws an error because the attribute project is incorrect

B. Terraform initializes and connects to the specified GCP project using the credentials file

C. Terraform ignores the credentials file and uses default credentials

D. Terraform creates a new GCP project named "my-project" automatically

Solution

1. Step 1: Check attribute names in the provider block

   The correct attribute for project ID is project, which is used here.

2. Step 2: Understand Terraform behavior on correct attributes

   Terraform initializes successfully and configures the provider using the credentials file.

3. Final Answer:

   Terraform initializes and connects to the specified GCP project using the credentials file -> Option B

4. Quick Check:

   Correct attributes allow successful init [OK]

Hint: Use exact attribute names like project to ensure smooth init [OK]

Common Mistakes:

• Assuming project is incorrect (it's the right attribute)
• Thinking Terraform auto-creates projects
• Believing init ignores credentials

4. You wrote this provider block:

provider "google" {
  project = "my-project"
  region = "us-central1"
  credentials = file("wrong-path.json")
}

When running terraform plan, you get a credentials error. What is the most likely cause?

medium

A. The credentials file path is incorrect or file does not exist

B. The project is invalid format

C. The region value is not supported by GCP

D. Terraform requires credentials to be set as environment variables only

Solution

1. Step 1: Analyze the credentials attribute

   The credentials attribute expects a valid JSON file path with service account keys.

2. Step 2: Identify the error cause

   If the file path is wrong or file missing, Terraform cannot authenticate and throws an error.

3. Final Answer:

   The credentials file path is incorrect or file does not exist -> Option A

4. Quick Check:

   Wrong credentials file path causes auth error [OK]

Hint: Check credentials file path carefully to avoid auth errors [OK]

Common Mistakes:

• Assuming region errors cause credential failures
• Thinking project format causes credential errors
• Believing credentials must be environment variables only

5. You want to configure Terraform to manage resources in two different GCP projects within the same configuration. How should you set up the provider blocks?

hard

A. Set project dynamically inside resource blocks without provider aliases

B. Use a single provider block with a list of projects

C. Create two separate Terraform configurations for each project

D. Define two provider blocks with different aliases and specify project for each

Solution

1. Step 1: Understand multi-project management in Terraform

   Terraform supports multiple provider configurations using aliases to distinguish them.

2. Step 2: Configure providers with aliases and project

   Define two provider "google" blocks with different alias names and set project for each.

3. Step 3: Reference providers in resources

   Use provider = google.alias_name in resource blocks to specify which project to use.

4. Final Answer:

   Define two provider blocks with different aliases and specify project for each -> Option D

5. Quick Check:

   Multiple projects = multiple aliased providers [OK]

Hint: Use provider aliases to manage multiple GCP projects [OK]

Common Mistakes:

• Trying to list multiple projects in one provider
• Not using aliases and causing conflicts
• Splitting into separate configs unnecessarily