Provider caching and mirrors in Terraform - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to specify the Terraform provider source.

Terraform

terraform {
  required_providers {
    aws = {
      source = "[1]"
      version = "~> 4.0"
    }
  }
}

Drag options to blanks, or click blank then click option'

Aaws/hashicorp

Bprovider/aws

Cterraform/aws

Dhashicorp/aws

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect source format like 'aws/hashicorp' or 'terraform/aws'.

Forgetting to specify the source at all.

The correct source for the AWS provider is hashicorp/aws. This tells Terraform to use the official AWS provider from HashiCorp.

2fill in blank

medium

Complete the code to configure a provider mirror for Terraform.

Terraform

provider_installation {
  filesystem_mirror {
    path    = "[1]"
    include = ["hashicorp/*"]
  }
  direct {
    exclude = ["hashicorp/*"]
  }
}

Drag options to blanks, or click blank then click option'

A/usr/local/providers

B/mnt/terraform-providers

C/etc/terraform/mirrors

D/var/lib/providers

Attempts:

3 left

💡 Hint

Common Mistakes

Using relative paths instead of absolute paths.

Choosing a path that does not exist or is not accessible.

The path should point to the directory where the provider mirror is stored. /mnt/terraform-providers is a common example path.

3fill in blank

hard

Fix the error in the provider installation block to correctly enable the mirror.

Terraform

provider_installation {
  [1] {
    path    = "/mnt/terraform-providers"
    include = ["hashicorp/*"]
  }
  direct {
    exclude = ["hashicorp/*"]
  }
}

Drag options to blanks, or click blank then click option'

Afilesystem_mirror

Bfile_mirror

Cmirror_filesystem

Dmirror

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect block names like 'file_mirror' or 'mirror_filesystem'.

Misspelling the block name.

The correct block name is filesystem_mirror. Other names will cause Terraform to fail parsing the configuration.

4fill in blank

hard

Fill both blanks to configure Terraform to use a mirror and fallback to direct installation.

Terraform

provider_installation {
  [1] {
    path    = "/opt/terraform/providers"
    include = ["[2]"]
  }
  direct {}
}

Drag options to blanks, or click blank then click option'

Afilesystem_mirror

Bhashicorp/*

Clocal_mirror

Dterraform/*

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect block names like 'local_mirror'.

Using wrong provider patterns like 'terraform/*'.

The block filesystem_mirror is used to specify a local mirror path. The include pattern hashicorp/* matches all providers from HashiCorp.

5fill in blank

hard

Fill all three blanks to configure Terraform with a mirror path, include pattern, and exclude pattern.

Terraform

provider_installation {
  [1] {
    path    = "/data/terraform/providers"
    include = ["[2]"]
  }
  direct {
    exclude = ["[3]"]
  }
}

Drag options to blanks, or click blank then click option'

Afilesystem_mirror

Bhashicorp/*

Dcustom/*

Attempts:

3 left

💡 Hint

Common Mistakes

Using the same pattern for include and exclude incorrectly.

Using wrong block names or patterns.

The filesystem_mirror block defines the mirror path. The include pattern hashicorp/* specifies which providers to use from the mirror. The direct block excludes custom/* providers from direct download, forcing them to use the mirror or fail.

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