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

website: Fix several broken links (#25808)

This commit is contained in:
Nick Fagerlund 2020-08-11 15:24:51 -07:00 committed by GitHub
parent 31f858e1bb
commit 2ffb71bcee
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
3 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
website/docs/configuration/modules.html.md
View File

@ -119,7 +119,7 @@ instance.
Full resource addresses for module contents are used within the UI and on the Full resource addresses for module contents are used within the UI and on the
command line, but cannot be used within a Terraform configuration. Only command line, but cannot be used within a Terraform configuration. Only
[outputs](docs/configuration/outputs.html) from a module can be referenced from [outputs](./outputs.html) from a module can be referenced from
elsewhere in your configuration. elsewhere in your configuration.
## Other Meta-arguments ## Other Meta-arguments

4
website/docs/configuration/providers.html.md
View File

@ -173,13 +173,13 @@ from their parents.
The `version` meta-argument specifies a version constraint for a provider, and The `version` meta-argument specifies a version constraint for a provider, and
works the same way as the `version` argument in a works the same way as the `version` argument in a
[`required_providers` block](./provider_requirements.html). The version [`required_providers` block](./provider-requirements.html). The version
constraint in a provider configuration is only used if `required_providers` constraint in a provider configuration is only used if `required_providers`
does not include one for that provider. does not include one for that provider.
**We do not recommend using the `version` argument in provider configurations.** **We do not recommend using the `version` argument in provider configurations.**
In Terraform 0.13 and later, version constraints should always be declared in In Terraform 0.13 and later, version constraints should always be declared in
[the `required_providers` block](./provider_requirements.html). [the `required_providers` block](./provider-requirements.html).
-> **Note:** The `version` meta-argument made sense before Terraform 0.13, since -> **Note:** The `version` meta-argument made sense before Terraform 0.13, since
Terraform could only install providers that were distributed by HashiCorp. Now Terraform could only install providers that were distributed by HashiCorp. Now

2
website/docs/internals/module-registry-protocol.html.md
View File

@ -81,7 +81,7 @@ blocks have the same source address.
## Service Discovery ## Service Discovery
The providers protocol begins with Terraform CLI using The providers protocol begins with Terraform CLI using
[./remote-service-discovery.html](Terraform's remote service discovery protocol), [Terraform's remote service discovery protocol](./remote-service-discovery.html),
with the hostname in the module address acting as the "User-facing Hostname". with the hostname in the module address acting as the "User-facing Hostname".
The service identifier for the module registry protocol is `modules.v1`. The service identifier for the module registry protocol is `modules.v1`.