TA-003 Question 77

Community Discussion

Written by other learners. Comments can disagree with the marked answer — check the official documentation when in doubt.

• 2

  Downloading a plugin directly from its origin registry is not always appropriate, though. For example, the system where you are running Terraform may not be able to access an origin registry due to firewall restrictions within your organization or your locality. To allow using Terraform providers in these situations, there are some alternative options for making provider plugins available to Terraform which we'll describe in the following sections. https://developer.hashicorp.com/terraform/language/providers/requirements#in-house-providers https://developer.hashicorp.com/terraform/cli/config/config-file#provider-installation

• Chose B1

  terraform can be used in AirGap region too

• Chose B3

  Terraform providers are not always installed from the Internet. While Terraform does fetch providers from the HashiCorp Terraform Registry by default, it also allows for the usage of providers from other sources or even local sources. Here's an example: terraform { required_providers { aws = { source = "hashicorp/aws" version = "2.70.0" } custom-provider = { source = "/path/to/local/custom-provider" } } } provider "aws" { region = "us-west-2" } provider "custom-provider" { # Configuration for the custom provider } In this example, the AWS provider is fetched from the HashiCorp Terraform Registry, while the "custom-provider" is loaded from a local path. The local provider must be properly compiled and placed in the specified path.