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
This commit is contained in:
Petros Kolyvas 2020-10-23 15:16:45 -03:00 committed by GitHub
parent ff94be21c2
commit b1671b2ce1
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 3 deletions

View File

@ -215,7 +215,7 @@ provider in a module, so you'll need to use a non-preferred name for at least
one of them. one of them.
When this happens, we recommend combining each provider's namespace with 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 ```hcl
terraform { terraform {
@ -223,11 +223,11 @@ terraform {
# In the rare situation of using two providers that # In the rare situation of using two providers that
# have the same type name -- "http" in this example -- # have the same type name -- "http" in this example --
# use a compound local name to distinguish them. # use a compound local name to distinguish them.
hashicorp_http = { hashicorp-http = {
source = "hashicorp/http" source = "hashicorp/http"
version = "~> 2.0" version = "~> 2.0"
} }
mycorp_http = { mycorp-http = {
source = "mycorp/http" source = "mycorp/http"
version = "~> 1.0" version = "~> 1.0"
} }