ResiLien
/
terraform
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

updated 'Module Sources' website documentation to be more clear about how 'HTTP URL' module sources work

This commit is contained in:
John Ritsema 2016-06-06 17:04:47 -04:00
parent 3d4bc56d97
commit c668c31203
1 changed files with 12 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
website/source/docs/modules/sources.html.markdown
View File

@ -29,6 +29,8 @@ Terraform supports the following sources:
* HTTP URLs * HTTP URLs
Note that all remote modules are git-based. The `HTTP URL` source redirects terraform to use another one of the sources.
Each is documented further below. Each is documented further below.
## Local File Paths ## Local File Paths
@ -194,8 +196,9 @@ parameters:
## HTTP URLs ## HTTP URLs
Any HTTP endpoint can serve up Terraform modules. For HTTP URLs (SSL is An HTTP URL can be used to redirect Terraform to get the module source from
supported, as well), Terraform will make a GET request to the given URL. one of the other sources. For HTTP URLs (SSL is supported, as well),
Terraform will make a GET request to the given URL.
An additional GET parameter `terraform-get=1` will be appended, allowing An additional GET parameter `terraform-get=1` will be appended, allowing
you to optionally render the page differently when Terraform is requesting it. you to optionally render the page differently when Terraform is requesting it.
@ -206,7 +209,13 @@ the source URL of the actual module. This will be used.
If the header isn't present, Terraform will look for a `<meta>` tag If the header isn't present, Terraform will look for a `<meta>` tag
with the name of "terraform-get". The value will be used as the source with the name of "terraform-get". The value will be used as the source
URL. URL.
Example:
```
<meta name=“terraform-get” content="github.com/hashicorp/example" />
```
## Forced Source Type ## Forced Source Type