Which module source path does not specify a remote module?

Which module source path does not specify a remote module?

• A. ./modules/consul
• B. git@github.com:hashicorp/example.git
• C. github.com/hashicorp/example
• D. hashicorp/consul/aws

Answer: (A)

Local module sources come from the filesystem and are not fetched from a remote location. A path that starts with ./ or ../ is treated as a local module path. The relative path ./modules/consul points to a directory named consul inside a modules folder of your project, which Terraform will load directly from disk. The other options describe locations outside your current project: a Git URL over SSH points to a repository, a domain-based path like github.com/hashicorp/example references a GitHub-hosted repository, and a namespace/provider path like hashicorp/consul/aws is resolved from the Terraform Registry. Therefore, the local filesystem path is the one that does not indicate a remote module.

Local module sources come from the filesystem and are not fetched from a remote location. A path that starts with ./ or ../ is treated as a local module path. The relative path ./modules/consul points to a directory named consul inside a modules folder of your project, which Terraform will load directly from disk. The other options describe locations outside your current project: a Git URL over SSH points to a repository, a domain-based path like github.com/hashicorp/example references a GitHub-hosted repository, and a namespace/provider path like hashicorp/consul/aws is resolved from the Terraform Registry. Therefore, the local filesystem path is the one that does not indicate a remote module.