website: Fix several broken links (#27091)

This commit is contained in:
Nick Fagerlund 2020-12-03 09:54:38 -08:00 committed by GitHub
parent 323cd4364b
commit 0c0749edcf
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
8 changed files with 15 additions and 13 deletions

View File

@ -10,7 +10,7 @@ description: |-
-> **Note:** This page is about Terraform 0.12 and later. For Terraform 0.11 and
earlier, see
[0.11 Configuration Language: Modules](../configuration-0-11/modules.html).
[0.11 Configuration Language: Modules](/docs/configuration-0-11/modules.html).
> **Hands-on:** Try the [Reuse Configuration with Modules](https://learn.hashicorp.com/collections/terraform/modules?utm_source=WEBSITE&utm_medium=WEB_IO&utm_offer=ARTICLE_PAGE&utm_content=DOCS) collection on HashiCorp Learn.

View File

@ -52,8 +52,8 @@ read-only attributes with information obtained from the remote API; this often
includes things that can't be known until the resource is created, like the
resource's unique random ID.
Many providers also include [data sources](./data-sources.html), which are a
special type of resource used only for looking up information.
Many providers also include [data sources](/docs/configuration/data-sources.html),
which are a special type of resource used only for looking up information.
For a list of the attributes a resource or data source type provides, consult
its documentation; these are generally included in a second list below its list
@ -83,8 +83,9 @@ However, some dependencies cannot be recognized implicitly in configuration. For
example, if Terraform must manage access control policies _and_ take actions
that require those policies to be present, there is a hidden dependency between
the access policy and a resource whose creation depends on it. In these rare
cases, [the `depends_on` meta-argument](./depends_on.html) can explicitly specify a
dependency.
cases,
[the `depends_on` meta-argument](/docs/configuration/meta-arguments/depends_on.html)
can explicitly specify a dependency.
## Local-only Resources

View File

@ -15,7 +15,7 @@ as DNS records.
- [Resource Blocks](/docs/configuration/blocks/resources/syntax.html) documents
the syntax for declaring resources.
- [Resource Behavior](/docs/configuration/resources/behavior.html) explains in
- [Resource Behavior](/docs/configuration/blocks/resources/behavior.html) explains in
more detail how Terraform handles resource declarations when applying a
configuration.

View File

@ -12,7 +12,7 @@ description: |-
-> **Note:** This page is about Terraform 0.12 and later. For Terraform 0.11 and
earlier, see
[0.11 Configuration Language: Resources](../configuration-0-11/resources.html).
[0.11 Configuration Language: Resources](/docs/configuration-0-11/resources.html).
> **Hands-on:** Try the [Terraform: Get Started](https://learn.hashicorp.com/collections/terraform/aws-get-started?utm_source=WEBSITE&utm_medium=WEB_IO&utm_offer=ARTICLE_PAGE&utm_content=DOCS) collection on HashiCorp Learn.

View File

@ -9,7 +9,7 @@ page_title: "Files and Directories - Configuration Language"
Code in the Terraform language is stored in plain text files with the `.tf` file
extension. There is also
[a JSON-based variant of the language](./syntax-json.html) that is named with
[a JSON-based variant of the language](/docs/configuration/syntax-json.html) that is named with
the `.tf.json` file extension.
Files containing Terraform code are often called _configuration files._

View File

@ -27,9 +27,6 @@ exposes an implementation for a specific service, such as AWS, or provisioner,
such as bash. Plugins are executed as a separate process and communicate with
the main Terraform binary over an RPC interface.
More details are available in
_[Plugin Internals](/docs/internals/internal-plugins.html)_.
The code within the binaries must adhere to certain interfaces.
The network communication and RPC is handled automatically by higher-level
Terraform libraries. The exact interface to implement is documented

View File

@ -188,7 +188,11 @@ block would create a dependency cycle.
## Suppressing Provisioner Logs in CLI Output
The configuration for a `provisioner` block may use sensitive values, such as [`sensitive` variables](../configuration/variables.html#suppressing-values-in-cli-output) or [`sensitive` output values](../outputs.html#sensitive-suppressing-values-in-cli-output). In this case, all log output from the provider is automatically suppressed to prevent the sensitive values from being displayed.
The configuration for a `provisioner` block may use sensitive values, such as
[`sensitive` variables](/docs/configuration/variables.html#suppressing-values-in-cli-output) or
[`sensitive` output values](/docs/configuration/outputs.html#sensitive-suppressing-values-in-cli-output).
In this case, all log output from the provisioner is automatically suppressed to
prevent the sensitive values from being displayed.
## Creation-Time Provisioners

View File

@ -48,7 +48,7 @@ terraform {
**Action:** Nothing immediately, everything will continue working
except scripts using `terraform remote config`.
As soon as possible, [upgrade to backends](/docs/backends/legacy-0-8.html).
As soon as possible, [upgrade to backends](/docs/configuration/blocks/backends/index.html).
## State Locking