Provider versioning constraints in Terraform - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to specify the AWS provider version constraint.

Terraform

terraform {
  required_providers {
    aws = {
      source  = "hashicorp/aws"
      version = [1]
    }
  }
}

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

A"^5.0"

B"~> 4.0"

C"= 3.0"

D"< 2.0"

Attempts:

3 left

💡 Hint

Common Mistakes

Using exact version '=' which is too restrictive.

Using '^' which is not supported in Terraform version constraints.

The version constraint "~> 4.0" means any version from 4.0 up to but not including 5.0, which is a common way to specify compatible provider versions.

2fill in blank

medium

Complete the code to require provider version 3.5 or higher but less than 4.0.

Terraform

terraform {
  required_providers {
    aws = {
      source  = "hashicorp/aws"
      version = [1]
    }
  }
}

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

A"= 3.5"

B"~> 3.5"

C">= 3.5, < 4.0"

D"< 3.5"

Attempts:

3 left

💡 Hint

Common Mistakes

Using '=' which fixes the version exactly.

Using '~> 3.5' instead of the range constraint.

The version constraint ">= 3.5, < 4.0" ensures the provider version is at least 3.5 but less than 4.0, allowing updates within the 3.x series.

3fill in blank

hard

Fix the error in the provider version constraint to allow any 2.x version.

Terraform

terraform {
  required_providers {
    aws = {
      source  = "hashicorp/aws"
      version = [1]
    }
  }
}

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

A"~> 2.0"

B"= 2"

C">= 2.0, < 3.0"

D"2.x"

Attempts:

3 left

💡 Hint

Common Mistakes

Using '=' with incomplete version number.

Using invalid version syntax like '2.x'.

The "~> 2.0" constraint allows any version starting from 2.0 up to but not including 3.0, which covers all 2.x versions.

4fill in blank

hard

Fill both blanks to specify the provider source and version constraint for Azure provider version 3.0 or higher but less than 4.0.

Terraform

terraform {
  required_providers {
    azure = {
      source  = [1]
      version = [2]
    }
  }
}

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

A"hashicorp/azurerm"

B"~> 3.0"

C">= 3.0, < 4.0"

D"hashicorp/azure"

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect provider source name.

Using '~> 3.0' instead of the range constraint.

The source for the Azure provider is "hashicorp/azurerm". The version constraint ">= 3.0, < 4.0" allows any version from 3.0 up to but not including 4.0.

5fill in blank

hard

Fill all three blanks to specify the Google provider with source, version constraint for any 4.x version, and a required Terraform version of at least 1.2.0.

Terraform

terraform {
  required_version = [1]
  required_providers {
    google = {
      source  = [2]
      version = [3]
    }
  }
}

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

A">= 1.2.0"

B"hashicorp/google"

C"~> 4.0"

D"= 4.0"

Attempts:

3 left

💡 Hint

Common Mistakes

Using '=' for provider version which fixes it exactly.

Using incorrect provider source name.

Setting required_version too low or too high.

The required_version sets the minimum Terraform version to ">= 1.2.0". The Google provider source is "hashicorp/google". The version constraint "~> 4.0" allows any 4.x version.

Practice

1. What is the main purpose of setting provider version constraints in Terraform?

easy

A. To speed up Terraform plan execution

B. To keep your infrastructure stable by controlling provider versions

C. To automatically upgrade providers to the latest version

D. To disable provider plugins

Solution

1. Step 1: Understand provider version constraints

   Provider version constraints tell Terraform which versions of a provider it can use.

2. Step 2: Identify the purpose of constraints

   They prevent unexpected changes by locking to specific versions or version ranges, keeping infrastructure stable.

3. Final Answer:

   To keep your infrastructure stable by controlling provider versions -> Option B

4. Quick Check:

   Provider version constraints = stability [OK]

Hint: Constraints keep provider versions stable to avoid surprises [OK]

Common Mistakes:

• Thinking constraints speed up execution
• Assuming constraints auto-upgrade providers
• Believing constraints disable providers

2. Which of the following is the correct syntax to specify a provider version constraint for AWS provider version 4.0 or higher but less than 5.0?

easy

A. terraform { required_providers { aws = ">= 4.0, < 5.0" } }

B. terraform { required_providers { aws = "~> 4.0.0" } }

C. terraform { required_providers { aws = "= 4.0" } }

D. terraform { required_providers { aws = "< 4.0" } }

Solution

1. Step 1: Understand version constraint syntax

   Using ">= 4.0, < 5.0" means versions starting at 4.0 up to but not including 5.0.

2. Step 2: Match syntax to requirement

   terraform { required_providers { aws = ">= 4.0, < 5.0" } } correctly uses this syntax inside the required_providers block.

3. Final Answer:

   terraform { required_providers { aws = ">= 4.0, < 5.0" } } -> Option A

4. Quick Check:

   Range constraint syntax = terraform { required_providers { aws = ">= 4.0, < 5.0" } } [OK]

Hint: Use ">= x, < y" for version ranges [OK]

Common Mistakes:

• Confusing ~> with exact version
• Using = for ranges
• Using < 4.0 instead of >= 4.0

3. Given this Terraform snippet, what provider version will be accepted?

terraform {
  required_providers {
    azurerm = "~> 3.5"
  }
}

medium

A. Any azurerm version 3.0.0 or higher

B. Only azurerm version 3.5.0 exactly

C. Any azurerm version 3.x.x including 4.0.0

D. Any azurerm version 3.5.x, but less than 4.0.0

Solution

1. Step 1: Understand the ~> operator

   The "~> 3.5" means any version starting at 3.5.0 up to but not including 4.0.0.

2. Step 2: Apply to azurerm provider

   So versions like 3.5.1, 3.6.0, 3.9.9 are allowed, but not 4.0.0 or higher.

3. Final Answer:

   Any azurerm version 3.5.x, but less than 4.0.0 -> Option D

4. Quick Check:

   ~> 3.5 means 3.5.x to <4.0.0 [OK]

Hint: ~> means compatible with minor version [OK]

Common Mistakes:

• Thinking ~> means exact version
• Allowing 4.0.0 or higher
• Confusing ~> with >= operator

4. You wrote this Terraform configuration but get an error about provider version conflict:

terraform {
  required_providers {
    google = ">= 3.0, < 4.0"
  }
}

provider "google" {
  version = "4.1.0"
}

What is the cause of the error?

medium

A. The required_providers block syntax is incorrect

B. The provider block is missing required credentials

C. The provider block version 4.1.0 is outside the required_providers constraint range

D. Terraform does not support version constraints

Solution

1. Step 1: Check required_providers constraint

   The constraint requires google provider version >= 3.0 and < 4.0.

2. Step 2: Check provider block version

   The provider block specifies version 4.1.0, which is outside the allowed range.

3. Final Answer:

   The provider block version 4.1.0 is outside the required_providers constraint range -> Option C

4. Quick Check:

   Version conflict due to mismatch [OK]

Hint: Provider version must fit required_providers range [OK]

Common Mistakes:

• Ignoring version mismatch
• Blaming syntax errors
• Assuming missing credentials cause version errors

5. You want to ensure your Terraform configuration always uses the latest patch version of AWS provider 4.12 but never upgrades to 4.13 or higher. Which version constraint should you use?

hard

A. "~> 4.12.0"

B. ">= 4.12.0"

C. "= 4.12.0"

D. "~> 4.12"

Solution

1. Step 1: Understand patch version constraints

   The "~> 4.12.0" means any version starting at 4.12.0 up to but not including 4.13.0, allowing patch updates.

2. Step 2: Compare with other options

   ">= 4.12.0" lacks upper bound, allowing upgrades to 4.13+; "= 4.12.0" locks to exact version; "~> 4.12" allows minor version upgrades beyond 4.12.x.

3. Final Answer:

   "~> 4.12.0" -> Option A

4. Quick Check:

   ~> with patch version locks minor, allows patches [OK]

Hint: Use ~> with patch to allow patch updates only [OK]

Common Mistakes:

• Using = to lock exact version, disallowing patches
• Using ~> 4.12 allowing minor upgrades
• Using lower bound only without upper limit