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.