From 11046cc60dcdc9639c8775a48cc8abe0d24cea7a Mon Sep 17 00:00:00 2001 From: Petros Kolyvas Date: Fri, 23 Oct 2020 15:16:45 -0300 Subject: [PATCH] website: Fix for documentation around local-name conflicts (#26689) * Fixes #26684 * Update provider-requirements.html.md Removing additional/extra newlines * Update provider-requirements.html.md And now some trailing spaces. le sigh --- website/docs/configuration/provider-requirements.html.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/website/docs/configuration/provider-requirements.html.md b/website/docs/configuration/provider-requirements.html.md index b27d85c2f4..c5e1c1cedd 100644 --- a/website/docs/configuration/provider-requirements.html.md +++ b/website/docs/configuration/provider-requirements.html.md @@ -215,7 +215,7 @@ provider in a module, so you'll need to use a non-preferred name for at least one of them. When this happens, we recommend combining each provider's namespace with -its type name to produce compound local names: +its type name to produce compound local names with a dash: ```hcl terraform { @@ -223,11 +223,11 @@ terraform { # In the rare situation of using two providers that # have the same type name -- "http" in this example -- # use a compound local name to distinguish them. - hashicorp_http = { + hashicorp-http = { source = "hashicorp/http" version = "~> 2.0" } - mycorp_http = { + mycorp-http = { source = "mycorp/http" version = "~> 1.0" }