Terraform GCP provider setup - Commands & Configuration

Introduction

Setting up Terraform to work with Google Cloud Platform lets you create and manage cloud resources using simple code. This setup connects Terraform to your GCP account so it can control your cloud projects safely and easily.

When you want to create a virtual machine in GCP using code instead of clicking in the console.

When you need to manage multiple GCP resources consistently across different environments.

When you want to automate cloud infrastructure setup for a new project in GCP.

When you want to keep your cloud setup in version control to track changes over time.

When you want to share your cloud setup with teammates so everyone uses the same configuration.

Config File - main.tf

main.tf

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

provider "google" {
  project = "example-project-123456"
  region  = "us-central1"
  credentials = file("./account-key.json")
}

This file tells Terraform to use the Google Cloud provider plugin version 4.0.0 or newer.

The provider "google" block sets your GCP project ID, region, and points to a JSON file with your service account credentials. This allows Terraform to authenticate and manage resources in your GCP project.

Commands

This command downloads the Google Cloud provider plugin and prepares Terraform to work with your configuration.

Terminal

terraform init

Expected Output

Initializing the backend...



Initializing provider plugins...

- Finding hashicorp/google versions matching ">= 4.0.0"...

- Installing hashicorp/google v4.50.0...

- Installed hashicorp/google v4.50.0 (signed by HashiCorp)



Terraform has been successfully initialized!



You may now begin working with Terraform. Try running "terraform plan" to see any changes that are required for your infrastructure.

This command checks your Terraform files for syntax errors and confirms the configuration is valid.

Terminal

terraform validate

Expected Output

Success! The configuration is valid.

This command shows what Terraform will do when you apply your configuration, without making any changes yet.

Terminal

terraform plan

Expected Output

No changes. Infrastructure is up-to-date.



This means that Terraform did not detect any differences between your configuration and the real infrastructure.

Key Concept

If you remember nothing else from this pattern, remember: the provider block connects Terraform to your GCP project using your credentials and project details.

Common Mistakes

Not providing the correct path to the service account JSON file in the credentials field.

Terraform cannot authenticate to GCP without valid credentials, so commands will fail with permission errors.

Make sure the credentials path points exactly to your downloaded service account JSON file, and the file has proper permissions.

Using the wrong project ID or region in the provider block.

Terraform will try to create resources in a project or region that does not exist or is not intended, causing errors or unexpected results.

Double-check your GCP project ID and region values before running Terraform commands.

Summary

Create a main.tf file with the Terraform block specifying the Google provider and version.

Add a provider block with your GCP project ID, region, and credentials file path.

Run 'terraform init' to download the provider plugin.

Use 'terraform validate' to check your configuration syntax.

Run 'terraform plan' to preview changes before applying.

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