From c668c312036c990374e7b6a6ee2f38bf8808412f Mon Sep 17 00:00:00 2001 From: John Ritsema Date: Mon, 6 Jun 2016 17:04:47 -0400 Subject: [PATCH] updated 'Module Sources' website documentation to be more clear about how 'HTTP URL' module sources work --- website/source/docs/modules/sources.html.markdown | 15 ++++++++++++--- 1 file changed, 12 insertions(+), 3 deletions(-) diff --git a/website/source/docs/modules/sources.html.markdown b/website/source/docs/modules/sources.html.markdown index d9e6a1316..89d774c60 100644 --- a/website/source/docs/modules/sources.html.markdown +++ b/website/source/docs/modules/sources.html.markdown @@ -29,6 +29,8 @@ Terraform supports the following sources: * 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. ## Local File Paths @@ -194,8 +196,9 @@ parameters: ## HTTP URLs -Any HTTP endpoint can serve up Terraform modules. For HTTP URLs (SSL is -supported, as well), Terraform will make a GET request to the given URL. +An HTTP URL can be used to redirect Terraform to get the module source from +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 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 `` tag with the name of "terraform-get". The value will be used as the source -URL. +URL. + +Example: + +``` + +``` ## Forced Source Type