From 9f45a73581bc113daca17aee88bcce83b825c598 Mon Sep 17 00:00:00 2001 From: Martin Atkins Date: Tue, 17 Nov 2020 16:17:46 -0800 Subject: [PATCH] website: Reword confusing statement about module sources in TFE As written previously this seemed to suggest using "app.terraform.io" (the "hostname you use to access the Terraform Cloud application) to access a private registry in Terraform Enterprise, but that isn't true and I assume isn't what was intended. Instead, the hostname for a Terraform Enterprise instance is the hostname where the Terraform Enterprise application is running, which is both the hostname where users would find its web UI and the hostname they'd use to configure the "remote" backend for remote operations and state storage. --- website/docs/modules/sources.html.markdown | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/website/docs/modules/sources.html.markdown b/website/docs/modules/sources.html.markdown index ec7c45e0b..72bf7c39e 100644 --- a/website/docs/modules/sources.html.markdown +++ b/website/docs/modules/sources.html.markdown @@ -116,9 +116,10 @@ module "consul" { ``` If you are using the SaaS version of Terraform Cloud, its private -registry hostname is `app.terraform.io`. If you are using a Terraform Enterprise -instance, its private registry hostname is the same hostname you use to -access the Terraform Cloud application. +registry hostname is `app.terraform.io`. If you use a self-hosted Terraform +Enterprise instance, its private registry hostname is the same as the host +where you'd access the web UI and the host you'd use when configuring +the `remote` backend. Registry modules support versioning. You can provide a specific version as shown in the above examples, or use flexible