Provider caching and mirrors in Terraform - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the purpose of provider caching in Terraform?

Provider caching stores downloaded provider plugins locally to speed up future Terraform runs and reduce network usage.

beginner

How do provider mirrors help in Terraform?

Provider mirrors act as local or private repositories that serve provider plugins, improving reliability and control over provider versions.

intermediate

Where does Terraform store cached providers by default?

Terraform stores cached providers in a hidden directory named .terraform/providers in the working directory and also in a global plugin cache directory.

intermediate

How can you configure Terraform to use a provider mirror?

You configure provider mirrors by setting the 'provider_installation' block in the CLI configuration file to point to the mirror URL or local path.

intermediate

Why is using provider mirrors beneficial in an offline or restricted network environment?

Provider mirrors allow Terraform to install providers without accessing the public internet, ensuring Terraform runs smoothly in offline or restricted networks.

What does Terraform use provider caching for?

A To store provider plugins locally for faster reuse

B To cache Terraform state files

C To save configuration files

D To backup cloud resources

Terraform caches provider plugins locally to avoid downloading them every time, speeding up runs.

Which file do you edit to configure provider mirrors in Terraform?

A terraform.tfvars

B CLI configuration file (e.g., ~/.terraformrc)

C main.tf

D provider.tf

Provider mirrors are configured in the CLI configuration file, such as ~/.terraformrc or terraform.rc.

What is a key benefit of using a provider mirror?

A Avoiding internet access for provider downloads

B Faster Terraform plan execution

C Automatically updating providers

D Encrypting provider plugins

Provider mirrors let Terraform download providers without internet access, useful in restricted environments.

Where does Terraform NOT store provider plugins by default?

A .terraform/providers directory

B Global plugin cache directory

C Local working directory

D Cloud provider's API

Terraform does not store provider plugins in the cloud provider's API; it caches them locally.

Which block is used to define provider installation methods including mirrors?

A terraform_block

B provider_config

C provider_installation

D plugin_cache

The 'provider_installation' block in the CLI config defines how Terraform installs providers, including mirrors.

Explain how provider caching and mirrors improve Terraform's performance and reliability.

Think about speed and network access.

Describe the steps to configure a provider mirror in Terraform.

Focus on the CLI config file and the provider_installation block.

Practice

1. What is the main purpose of provider caching in Terraform?

easy

A. To encrypt provider plugins for security

B. To store provider plugins locally and speed up Terraform runs

C. To delete unused providers automatically

D. To force Terraform to always download providers from the internet

Solution

1. Step 1: Understand provider caching concept

   Provider caching means saving provider plugins on your local machine so Terraform doesn't need to download them every time.

2. Step 2: Identify the benefit of caching

   This local storage speeds up Terraform runs by avoiding repeated downloads.

3. Final Answer:

   To store provider plugins locally and speed up Terraform runs -> Option B

4. Quick Check:

   Provider caching = local storage for speed [OK]

Hint: Caching means saving locally to avoid repeated downloads [OK]

Common Mistakes:

• Thinking caching deletes providers
• Confusing caching with encryption
• Assuming caching forces downloads

2. Which block is used in Terraform configuration to specify a local directory for provider caching?

easy

A. direct

B. cache_location

C. filesystem_mirror

D. provider_cache

Solution

1. Step 1: Recall Terraform provider mirror blocks

   Terraform uses filesystem_mirror blocks to define local directories for caching providers.

2. Step 2: Confirm correct block name

   The direct block is for direct downloads, not caching. Other options are invalid.

3. Final Answer:

   filesystem_mirror -> Option C

4. Quick Check:

   Local cache directory = filesystem_mirror [OK]

Hint: Filesystem mirror means local cache folder [OK]

Common Mistakes:

• Confusing direct with caching block
• Using non-existent block names
• Assuming provider_cache is valid

3. Given this Terraform CLI configuration snippet:

provider_installation {
  filesystem_mirror {
    path    = "/cache/providers"
  }
  direct {
    exclude = ["hashicorp/aws"]
  }
}

What happens when Terraform needs the hashicorp/aws provider?

medium

A. Terraform downloads hashicorp/aws directly from the internet

B. Terraform uses the cached version from /cache/providers

C. Terraform throws an error because hashicorp/aws is excluded

D. Terraform ignores the provider and continues without it

Solution

1. Step 1: Analyze the filesystem_mirror and direct blocks

   The filesystem_mirror caches providers locally except those excluded in direct.

2. Step 2: Understand the exclude setting

   The direct block excludes hashicorp/aws, so Terraform will not use the cache for it.

3. Step 3: Determine provider source

   Terraform downloads hashicorp/aws directly from the internet.

4. Final Answer:

   Terraform downloads hashicorp/aws directly from the internet -> Option A

5. Quick Check:

   Exclude means direct download [OK]

Hint: Exclude in direct means download from internet [OK]

Common Mistakes:

• Assuming excluded providers use cache
• Thinking exclusion causes errors
• Believing providers are ignored if excluded

4. You configured a filesystem_mirror path but Terraform still downloads providers from the internet. What is the most likely cause?

medium

A. The filesystem_mirror path is incorrect or inaccessible

B. Terraform does not support provider caching

C. You forgot to install Terraform CLI

D. The provider version is not specified in configuration

Solution

1. Step 1: Check filesystem_mirror path validity

   If the path is wrong or Terraform cannot access it, caching won't work and providers download from the internet.

2. Step 2: Rule out other causes

   Terraform supports caching, CLI must be installed, and version absence doesn't force downloads if cache is valid.

3. Final Answer:

   The filesystem_mirror path is incorrect or inaccessible -> Option A

4. Quick Check:

   Invalid cache path causes downloads [OK]

Hint: Check cache path accessibility first [OK]

Common Mistakes:

• Assuming Terraform lacks caching support
• Ignoring filesystem permissions
• Blaming missing provider version

5. You want to speed up Terraform runs in a team by caching providers locally but still allow direct downloads for some custom providers. Which configuration correctly achieves this?

hard

A. provider_installation {
direct {
include = ["customcorp/custom"]
}
filesystem_mirror {
path = "/team/cache"
}
}

B. provider_installation {
direct {
path = "/team/cache"
}
filesystem_mirror {
exclude = ["customcorp/custom"]
}
}

C. provider_installation {
filesystem_mirror {
exclude = ["customcorp/custom"]
}
direct {
path = "/team/cache"
}
}

D. provider_installation {
filesystem_mirror {
path = "/team/cache"
}
direct {
exclude = ["customcorp/custom"]
}
}

Solution

1. Step 1: Understand correct block usage

   filesystem_mirror defines the local cache path; direct defines providers to download directly.

2. Step 2: Check correct syntax and order

   provider_installation {
     filesystem_mirror {
       path = "/team/cache"
     }
     direct {
       exclude = ["customcorp/custom"]
     }
   }

   correctly sets filesystem_mirror with path and direct with exclude list for custom providers.

3. Step 3: Identify incorrect options

   Other options misuse keys or swap path and exclude incorrectly.

4. Final Answer:

   provider_installation {
     filesystem_mirror {
       path = "/team/cache"
     }
     direct {
       exclude = ["customcorp/custom"]
     }
   }

   -> Option D

5. Quick Check:

   Cache path in filesystem_mirror, exclude in direct [OK]

Hint: Cache path in filesystem_mirror, exclude in direct block [OK]

Common Mistakes:

• Swapping path and exclude keys
• Putting exclude in filesystem_mirror
• Misplacing blocks order