To access a non-public Git repository, configure Git with So it will respect any local Git configuration set on your system, includingĬredentials. Terraform installs modules from Git repositories by running git clone, and Module's information page on the registry site including the exact address Modules on the public Terraform Registry can be referenced using a registry Via the built-in feature from Terraform Cloud, or by running a custom To get started with Terraform and find modules created by others in the Terraform Registry is an index of modules Terraform RegistryĪ module registry is the native way of distributing Terraform modules for useĪcross multiple configurations, using a Terraform-specific protocol that
Modules, because it will tend to couple your configuration to the filesystem We don't recommend using absolute filesystem paths to refer to Terraform An absolute path is a "package" in the sense described Terraform will treat that in a similar way as a remote module and copy it into With a slash, a drive letter, or similar) to be a local path. Note that Terraform does not consider an absolute filesystem path (starting Their source code is automatically updated if the parent module is upgraded. That other sources are: the files are already present on local disk (possiblyĪs a result of installing a parent module) and so can just be used directly. 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.
0 kommentar(er)
