GCP provider setup in Terraform - Commands & Configuration

Introduction

When you want to create and manage Google Cloud resources using Terraform, you need to set up the GCP provider. This setup connects Terraform to your Google Cloud account so it can create, update, or delete resources for you.

When you want to automate creating virtual machines in Google Cloud.

When you need to manage Google Cloud storage buckets with code.

When you want to keep your cloud infrastructure consistent and repeatable.

When you want to track changes to your Google Cloud setup in version control.

When you want to quickly recreate your Google Cloud environment in another project or region.

Config File - main.tf

main.tf

terraform {
  required_providers {
    google = {
      source  = "hashicorp/google"
      version = ">= 4.0.0"
    }
  }
  required_version = ">= 1.3.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. It sets the Google Cloud project ID and region where resources will be created. The credentials key points to a JSON file with your service account key, which allows Terraform to access your Google Cloud account securely.

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 shows what Terraform will do when you apply your configuration. It checks your setup and the current state of your Google Cloud resources.

Terminal

terraform plan

Expected Output

Refreshing Terraform state in-memory prior to plan...



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 Google Cloud account so it can manage resources there.

Common Mistakes

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

Terraform cannot authenticate to Google Cloud without valid credentials, so it will fail to create or manage resources.

Make sure the credentials path points to a valid JSON key file downloaded from your Google Cloud service account.

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 that you do not have access to, causing errors.

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

Summary

Create a main.tf file with the Google Cloud provider block including project, region, and credentials.

Run 'terraform init' to download the provider plugin and prepare Terraform.

Run 'terraform plan' to verify Terraform can connect and see what changes it will make.