GCP provider setup in Terraform - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the purpose of the GCP provider in Terraform?

The GCP provider allows Terraform to interact with Google Cloud Platform services by managing resources like compute instances, storage buckets, and networks.

beginner

Which Terraform block is used to configure the GCP provider?

The provider "google" block is used to configure the GCP provider with credentials, project ID, and region.

beginner

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

You specify them using the project and region arguments inside the provider "google" block.

intermediate

What is the recommended way to provide credentials for the GCP provider in Terraform?

Use a service account key file and set the credentials argument to the file path, or set the GOOGLE_APPLICATION_CREDENTIALS environment variable.

intermediate

Why is it important to pin the provider version in Terraform configuration?

Pinning the provider version ensures consistent behavior and avoids unexpected changes when new provider versions are released.

Which block do you use to configure the GCP provider in Terraform?

A provider "google"

B resource "google"

C module "google"

D variable "google"

The provider "google" block configures the GCP provider.

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

A project = "your-project-id" inside provider block

B region = "your-project-id" inside provider block

C project_id = "your-project-id" inside resource block

D project_name = "your-project-id" inside variable block

The project argument inside the provider block sets the GCP project.

What is the best way to provide credentials to the GCP provider?

A Use anonymous access

B Hardcode username and password in provider block

C Use a service account key file or environment variable

D No credentials needed

Using a service account key file or the GOOGLE_APPLICATION_CREDENTIALS environment variable is secure and recommended.

Why should you pin the provider version in Terraform?

A To make Terraform run faster

B To reduce the size of Terraform files

C To allow automatic upgrades

D To avoid unexpected changes from new provider versions

Pinning the version ensures consistent behavior and avoids surprises.

Which environment variable can be used to provide GCP credentials to Terraform?

A GOOGLE_CLOUD_KEY

B GOOGLE_APPLICATION_CREDENTIALS

C TF_VAR_credentials

D GCP_CREDENTIALS_PATH

The GOOGLE_APPLICATION_CREDENTIALS environment variable points to the service account key file.

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

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

Describe why managing credentials securely is important when configuring the GCP provider.

Consider risks of leaking credentials and how to prevent them.

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