Terraform GCP provider setup - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the purpose of the Terraform GCP provider?

The Terraform GCP provider allows Terraform to manage and interact with Google Cloud Platform resources by translating Terraform configurations into API calls to GCP.

beginner

How do you specify the GCP project and region in the Terraform provider configuration?

You specify the project and region inside the provider block using the 'project' and 'region' attributes, for example:

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

intermediate

What authentication methods can Terraform use to connect to GCP?

Terraform can authenticate to GCP using:
- Application Default Credentials (ADC)
- Service Account JSON key file
- Environment variables pointing to credentials
This allows Terraform to securely access GCP resources.

beginner

What is the minimum Terraform block needed to initialize the GCP provider?

A minimal provider block looks like:

provider "google" {
  project = "your-project-id"
  region  = "your-region"
}

This tells Terraform which GCP project and region to use.

beginner

Why is it important to run 'terraform init' after adding the GCP provider?

'terraform init' downloads the GCP provider plugin and sets up the working directory so Terraform can communicate with GCP. Without it, Terraform cannot apply or plan changes.

Which block in Terraform config specifies the GCP provider?

A provider "google" {}

B resource "google" {}

C module "google" {}

D variable "google" {}

The provider block with name "google" configures the GCP provider.

How does Terraform authenticate to GCP using a service account?

A By using the 'region' attribute

B By specifying the project ID only

C By running 'terraform apply' without config

D By setting the 'credentials' attribute with the path to the JSON key file

Terraform uses the 'credentials' attribute to point to the service account JSON key file for authentication.

What command must you run to download the GCP provider plugin after adding it to your config?

A terraform plan

B terraform init

C terraform apply

D terraform validate

'terraform init' downloads provider plugins and initializes the working directory.

Which attribute is NOT part of the GCP provider configuration?

A instance_type

B region

C credentials

D project

'instance_type' is a resource attribute, not a provider configuration attribute.

What environment variable can Terraform use to find GCP credentials automatically?

A GCP_PROJECT_ID

B TERRAFORM_CREDENTIALS

C GOOGLE_APPLICATION_CREDENTIALS

D GOOGLE_REGION

The 'GOOGLE_APPLICATION_CREDENTIALS' environment variable points to the JSON key file for authentication.

Explain how to set up the Terraform GCP provider from scratch.

Think about what Terraform needs to connect and manage GCP resources.

Describe the role of the 'terraform init' command in the GCP provider setup.

Consider what happens before you can plan or apply changes.

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