Local paths are special in that they are not 'installed' in the same sense Local path references allow for factoring out portions of a configurationĪ local path must begin with either. Of its own repository or archive file, but it is also possible to We recommend placing each module that is intended to be re-usable in the root This is covered in more detail in each of the following When Terraform is run, such as from environment variables or credentials files Many of the source types will make use of 'ambient' credentials available Terraform modules internally with existing infrastructure. We support other sources so that you can potentially distribute Terraform module registry for modules intended to be shared by multiple callingĬonfigurations. We recommend using local file paths for closely-related modules used primarilyįor the purpose of factoring out repeated code elements, and using a native

Use a URL-like syntax, but with extensions to support unambiguous selection The module installer supports installation from a number of different sourceĮach of these is described in the following sections. Hands-on: Try the Use Modules From the Registry or Build and Use a Local Module tutorials. To download the source code to a directory on local disk so that other Terraform commands can use it. Terraform uses this during the module installation step of terraform init Tells Terraform where to find the source code for the desired child module.

Git remote repository not found