diff --git a/website/docs/backends/types/azurerm.html.md b/website/docs/backends/types/azurerm.html.md index 7b4de9769..f2b7fa3c7 100644 --- a/website/docs/backends/types/azurerm.html.md +++ b/website/docs/backends/types/azurerm.html.md @@ -146,9 +146,9 @@ data "terraform_remote_state" "foo" { The following configuration options are supported: -* `storage_account_name` - (Required) The Name of [the Storage Account](https://www.terraform.io/docs/providers/azurerm/r/storage_account.html). +* `storage_account_name` - (Required) The Name of [the Storage Account](https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/resources/storage_account). -* `container_name` - (Required) The Name of [the Storage Container](https://www.terraform.io/docs/providers/azurerm/r/storage_container.html) within the Storage Account. +* `container_name` - (Required) The Name of [the Storage Container](https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/resources/storage_container) within the Storage Account. * `key` - (Required) The name of the Blob used to retrieve/store Terraform's State file inside the Storage Container. diff --git a/website/docs/backends/types/cos.html.md b/website/docs/backends/types/cos.html.md index e063fc2aa..0a0173eee 100644 --- a/website/docs/backends/types/cos.html.md +++ b/website/docs/backends/types/cos.html.md @@ -28,7 +28,7 @@ terraform { } ``` -This assumes we have a [COS Bucket](https://www.terraform.io/docs/providers/tencentcloud/r/cos_bucket.html) created named `bucket-for-terraform-state-1258798060`, +This assumes we have a [COS Bucket](https://registry.terraform.io/providers/tencentcloudstack/tencentcloud/latest/docs/resources/cos_bucket) created named `bucket-for-terraform-state-1258798060`, Terraform state will be written into the file `terraform/state/terraform.tfstate`. ## Data Source Configuration diff --git a/website/docs/backends/types/oss.html.md b/website/docs/backends/types/oss.html.md index b3fbd828e..bcf6e42e4 100644 --- a/website/docs/backends/types/oss.html.md +++ b/website/docs/backends/types/oss.html.md @@ -33,9 +33,9 @@ terraform { } ``` -This assumes we have a [OSS Bucket](https://www.terraform.io/docs/providers/alicloud/r/oss_bucket.html) created called `bucket-for-terraform-state`, -a [OTS Instance](https://www.terraform.io/docs/providers/alicloud/r/ots_instance.html) called `terraform-remote` and -a [OTS TableStore](https://www.terraform.io/docs/providers/alicloud/r/ots_table.html) called `statelock`. The +This assumes we have a [OSS Bucket](https://registry.terraform.io/providers/aliyun/alicloud/latest/docs/resources/oss_bucket) created called `bucket-for-terraform-state`, +a [OTS Instance](https://registry.terraform.io/providers/aliyun/alicloud/latest/docs/resources/ots_instance) called `terraform-remote` and +a [OTS TableStore](https://registry.terraform.io/providers/aliyun/alicloud/latest/docs/resources/ots_table) called `statelock`. The Terraform state will be written into the file `path/mystate/version-1.tfstate`. The `TableStore` must have a primary key named `LockID` of type `String`. diff --git a/website/docs/configuration-0-11/interpolation.html.md b/website/docs/configuration-0-11/interpolation.html.md index 7178cd215..80102490a 100644 --- a/website/docs/configuration-0-11/interpolation.html.md +++ b/website/docs/configuration-0-11/interpolation.html.md @@ -449,7 +449,7 @@ Terraform 0.12 and later. ## Templates Long strings can be managed using templates. -[Templates](/docs/providers/template/index.html) are +[Templates](https://registry.terraform.io/providers/hashicorp/template/latest/docs) are [data-sources](./data-sources.html) defined by a string with interpolation tokens (usually loaded from a file) and some variables to use during interpolation. They have a computed `rendered` attribute @@ -487,7 +487,7 @@ by the surrounding scope of the configuration. You may use any of the built-in functions in your template. For more details on template usage, please see the -[template_file documentation](/docs/providers/template/d/file.html). +[template_file documentation](https://registry.terraform.io/providers/hashicorp/template/latest/docs/data-sources/file). ### Using Templates with Count diff --git a/website/docs/configuration-0-11/resources.html.md b/website/docs/configuration-0-11/resources.html.md index f6b3b56d4..db0172781 100644 --- a/website/docs/configuration-0-11/resources.html.md +++ b/website/docs/configuration-0-11/resources.html.md @@ -98,7 +98,7 @@ There are **meta-parameters** available to all resources: Individual Resources may provide a `timeouts` block to enable users to configure the amount of time a specific operation is allowed to take before being considered an error. For example, the -[aws_db_instance](/docs/providers/aws/r/db_instance.html#timeouts) +[aws_db_instance](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/db_instance#timeouts) resource provides configurable timeouts for the `create`, `update`, and `delete` operations. Any Resource that provides Timeouts will document the default values for that operation, and users can overwrite @@ -211,7 +211,7 @@ You can use the `${count.index}` [variable](./variables.html) to accomplish this. For example, here's how you could create three [AWS -Instances](/docs/providers/aws/r/instance.html) each with their own +Instances](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/instance) each with their own static IP address: ```hcl @@ -232,7 +232,7 @@ resource "aws_instance" "app" { To reference a particular instance of a resource you can use `resource.foo.*.id[#]` where `#` is the index number of the instance. -For example, to create a list of all [AWS subnet](/docs/providers/aws/r/subnet.html) ids vs referencing a specific subnet in the list you can use this syntax: +For example, to create a list of all [AWS subnet](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/subnet) ids vs referencing a specific subnet in the list you can use this syntax: ```hcl resource "aws_vpc" "foo" { diff --git a/website/docs/configuration/blocks/resources/behavior.html.md b/website/docs/configuration/blocks/resources/behavior.html.md index c5ecd2f31..b565e0abf 100644 --- a/website/docs/configuration/blocks/resources/behavior.html.md +++ b/website/docs/configuration/blocks/resources/behavior.html.md @@ -95,9 +95,9 @@ types that operate only within Terraform itself, calculating some results and saving those results in the state for future use. For example, local-only resource types exist for -[generating private keys](/docs/providers/tls/r/private_key.html), -[issuing self-signed TLS certificates](/docs/providers/tls/r/self_signed_cert.html), -and even [generating random ids](/docs/providers/random/r/id.html). +[generating private keys](https://registry.terraform.io/providers/hashicorp/tls/latest/docs/resources/private_key), +[issuing self-signed TLS certificates](https://registry.terraform.io/providers/hashicorp/tls/latest/docs/resources/self_signed_cert), +and even [generating random ids](https://registry.terraform.io/providers/hashicorp/random/latest/docs/resources/id). While these resource types often have a more marginal purpose than those managing "real" infrastructure objects, they can be useful as glue to help connect together other resources. diff --git a/website/docs/configuration/blocks/resources/syntax.html.md b/website/docs/configuration/blocks/resources/syntax.html.md index c2ed06a48..2f74015d1 100644 --- a/website/docs/configuration/blocks/resources/syntax.html.md +++ b/website/docs/configuration/blocks/resources/syntax.html.md @@ -46,7 +46,7 @@ resource and so must be unique within a module. Within the block body (between `{` and `}`) are the configuration arguments for the resource itself. Most arguments in this section depend on the resource type, and indeed in this example both `ami` and `instance_type` are -arguments defined specifically for [the `aws_instance` resource type](/docs/providers/aws/r/instance.html). +arguments defined specifically for [the `aws_instance` resource type](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/instance). -> **Note:** Resource names must start with a letter or underscore, and may contain only letters, digits, underscores, and dashes. @@ -144,7 +144,7 @@ The following meta-arguments are documented on separate pages: Some resource types provide a special `timeouts` nested block argument that allows you to customize how long certain operations are allowed to take before being considered to have failed. -For example, [`aws_db_instance`](/docs/providers/aws/r/db_instance.html) +For example, [`aws_db_instance`](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/db_instance) allows configurable timeouts for `create`, `update` and `delete` operations. Timeouts are handled entirely by the resource type implementation in the diff --git a/website/docs/configuration/data-sources.html.md b/website/docs/configuration/data-sources.html.md index 33c1d679e..8cb59014f 100644 --- a/website/docs/configuration/data-sources.html.md +++ b/website/docs/configuration/data-sources.html.md @@ -49,7 +49,7 @@ resource and so must be unique within a module. Within the block body (between `{` and `}`) are query constraints defined by the data source. Most arguments in this section depend on the data source, and indeed in this example `most_recent`, `owners` and `tags` are -all arguments defined specifically for [the `aws_ami` data source](/docs/providers/aws/d/ami.html). +all arguments defined specifically for [the `aws_ami` data source](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/data-sources/ami). When distinguishing from data resources, the primary kind of resource (as declared by a `resource` block) is known as a _managed resource_. Both kinds of resources @@ -103,9 +103,9 @@ only within Terraform itself, calculating some results and exposing them for use elsewhere. For example, local-only data sources exist for -[rendering templates](/docs/providers/template/d/file.html), -[reading local files](/docs/providers/local/d/file.html), and -[rendering AWS IAM policies](/docs/providers/aws/d/iam_policy_document.html). +[rendering templates](https://registry.terraform.io/providers/hashicorp/template/latest/docs/data-sources/file), +[reading local files](https://registry.terraform.io/providers/hashicorp/local/latest/docs/data-sources/file), and +[rendering AWS IAM policies](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/data-sources/iam_policy_document). The behavior of local-only data sources is the same as all other data sources, but their result data exists only temporarily during a Terraform diff --git a/website/docs/configuration/expressions/references.html.md b/website/docs/configuration/expressions/references.html.md index 59d2b413e..86d562108 100644 --- a/website/docs/configuration/expressions/references.html.md +++ b/website/docs/configuration/expressions/references.html.md @@ -213,7 +213,7 @@ resource "aws_instance" "example" { } ``` -The documentation for [`aws_instance`](/docs/providers/aws/r/instance.html) +The documentation for [`aws_instance`](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/instance) lists all of the arguments and nested blocks supported for this resource type, and also lists a number of attributes that are _exported_ by this resource type. All of these different resource type schema constructs are available diff --git a/website/docs/configuration/functions/file.html.md b/website/docs/configuration/functions/file.html.md index 71fdeb831..dc83b4f1a 100644 --- a/website/docs/configuration/functions/file.html.md +++ b/website/docs/configuration/functions/file.html.md @@ -31,7 +31,7 @@ dependency graph, so this function cannot be used with files that are generated dynamically during a Terraform operation. We do not recommend using dynamic local files in Terraform configurations, but in rare situations where this is necessary you can use -[the `local_file` data source](/docs/providers/local/d/file.html) +[the `local_file` data source](https://registry.terraform.io/providers/hashicorp/local/latest/docs/data-sources/file) to read files while respecting resource dependencies. ## Examples diff --git a/website/docs/configuration/functions/uuid.html.md b/website/docs/configuration/functions/uuid.html.md index 40ef135d9..7ed9ba9bc 100644 --- a/website/docs/configuration/functions/uuid.html.md +++ b/website/docs/configuration/functions/uuid.html.md @@ -25,11 +25,11 @@ recommend using the `uuid` function in resource configurations, but it can be used with care in conjunction with [the `ignore_changes` lifecycle meta-argument](/docs/configuration/meta-arguments/lifecycle.html#ignore_changes). -In most cases we recommend using [the `random` provider](/docs/providers/random/index.html) +In most cases we recommend using [the `random` provider](https://registry.terraform.io/providers/hashicorp/random/latest/docs) instead, since it allows the one-time generation of random values that are then retained in the Terraform [state](/docs/state/index.html) for use by future operations. In particular, -[`random_id`](/docs/providers/random/r/id.html) can generate results with +[`random_id`](https://registry.terraform.io/providers/hashicorp/random/latest/docs/resources/id) can generate results with equivalent randomness to the `uuid` function. ## Examples diff --git a/website/docs/modules/composition.html.markdown b/website/docs/modules/composition.html.markdown index 1f64b8e49..695690e7a 100644 --- a/website/docs/modules/composition.html.markdown +++ b/website/docs/modules/composition.html.markdown @@ -345,11 +345,11 @@ module "k8s_cluster" { The `network` module itself could retrieve this data in a number of different ways: it could query the AWS API directly using -[`aws_vpc`](/docs/providers/aws/d/vpc.html) +[`aws_vpc`](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/data-sources/vpc) and -[`aws_subnet_ids`](/docs/providers/aws/d/subnet_ids.html) +[`aws_subnet_ids`](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/data-sources/subnet_ids) data sources, or it could read saved information from a Consul cluster using -[`consul_keys`](https://www.terraform.io/docs/providers/consul/d/keys.html), +[`consul_keys`](https://registry.terraform.io/providers/hashicorp/consul/latest/docs/data-sources/keys), or it might read the outputs directly from the state of the configuration that manages the network using [`terraform_remote_state`](https://www.terraform.io/docs/providers/terraform/d/remote_state.html). diff --git a/website/docs/provisioners/file.html.markdown b/website/docs/provisioners/file.html.markdown index 9ace6b847..1d6770a83 100644 --- a/website/docs/provisioners/file.html.markdown +++ b/website/docs/provisioners/file.html.markdown @@ -59,7 +59,7 @@ The following arguments are supported: * `content` - This is the content to copy on the destination. If destination is a file, the content will be written on that file, in case of a directory a file named `tf-file-content` is created. It's recommended to use a file as the destination. A - [`template_file`](/docs/providers/template/d/file.html) might be referenced in here, or + [`template_file`](https://registry.terraform.io/providers/hashicorp/template/latest/docs/data-sources/file) might be referenced in here, or any interpolation syntax. This attribute cannot be specified with `source`. * `destination` - (Required) This is the destination path. It must be specified as an diff --git a/website/docs/provisioners/index.html.markdown b/website/docs/provisioners/index.html.markdown index e993dfe6f..6a9f266ba 100644 --- a/website/docs/provisioners/index.html.markdown +++ b/website/docs/provisioners/index.html.markdown @@ -50,25 +50,25 @@ to pass data to instances at the time of their creation such that the data is immediately available on system boot. For example: * Alibaba Cloud: `user_data` on - [`alicloud_instance`](/docs/providers/alicloud/r/instance.html) - or [`alicloud_launch_template`](/docs/providers/alicloud/r/launch_template.html). + [`alicloud_instance`](https://registry.terraform.io/providers/aliyun/alicloud/latest/docs/resources/instance) + or [`alicloud_launch_template`](https://registry.terraform.io/providers/aliyun/alicloud/latest/docs/resources/launch_template). * Amazon EC2: `user_data` or `user_data_base64` on - [`aws_instance`](/docs/providers/aws/r/instance.html), - [`aws_launch_template`](/docs/providers/aws/r/launch_template.html), - and [`aws_launch_configuration`](/docs/providers/aws/r/launch_configuration.html). + [`aws_instance`](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/instance), + [`aws_launch_template`](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/launch_template), + and [`aws_launch_configuration`](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/launch_configuration). * Amazon Lightsail: `user_data` on - [`aws_lightsail_instance`](/docs/providers/aws/r/lightsail_instance.html). + [`aws_lightsail_instance`](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/lightsail_instance). * Microsoft Azure: `custom_data` on - [`azurerm_virtual_machine`](/docs/providers/azurerm/r/virtual_machine.html) - or [`azurerm_virtual_machine_scale_set`](/docs/providers/azurerm/r/virtual_machine_scale_set.html). + [`azurerm_virtual_machine`](https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/resources/virtual_machine) + or [`azurerm_virtual_machine_scale_set`](https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/resources/virtual_machine_scale_set). * Google Cloud Platform: `metadata` on - [`google_compute_instance`](/docs/providers/google/r/compute_instance.html) - or [`google_compute_instance_group`](/docs/providers/google/r/compute_instance_group.html). + [`google_compute_instance`](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/compute_instance) + or [`google_compute_instance_group`](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/compute_instance_group). * Oracle Cloud Infrastructure: `metadata` or `extended_metadata` on - [`oci_core_instance`](/docs/providers/oci/r/core_instance.html) - or [`oci_core_instance_configuration`](/docs/providers/oci/r/core_instance_configuration.html). + [`oci_core_instance`](https://registry.terraform.io/providers/hashicorp/oci/latest/docs/resources/core_instance) + or [`oci_core_instance_configuration`](https://registry.terraform.io/providers/hashicorp/oci/latest/docs/resources/core_instance_configuration). * VMware vSphere: Attach a virtual CDROM to - [`vsphere_virtual_machine`](/docs/providers/vsphere/r/virtual_machine.html) + [`vsphere_virtual_machine`](https://registry.terraform.io/providers/hashicorp/vsphere/latest/docs/resources/virtual_machine) using the `cdrom` block, containing a file called `user-data.txt`. Many official Linux distribution disk images include software called diff --git a/website/docs/provisioners/null_resource.html.markdown b/website/docs/provisioners/null_resource.html.markdown index 61c221fb9..8ee6f62f9 100644 --- a/website/docs/provisioners/null_resource.html.markdown +++ b/website/docs/provisioners/null_resource.html.markdown @@ -9,7 +9,7 @@ description: |- # Provisioners Without a Resource -[null]: /docs/providers/null/resource.html +[null]: https://registry.terraform.io/providers/hashicorp/null/latest/docs/resources/resource If you need to run provisioners that aren't directly associated with a specific resource, you can associate them with a `null_resource`. diff --git a/website/docs/state/remote.html.md b/website/docs/state/remote.html.md index 4187542c8..2aa47f002 100644 --- a/website/docs/state/remote.html.md +++ b/website/docs/state/remote.html.md @@ -46,9 +46,9 @@ between configurations, you may prefer to use more general stores to pass settings both to other configurations and to other consumers. For example, if your environment has [HashiCorp Consul](https://www.consul.io/) then you can have one Terraform configuration that writes to Consul using -[`consul_key_prefix`](/docs/providers/consul/r/key_prefix.html) and then +[`consul_key_prefix`](https://registry.terraform.io/providers/hashicorp/consul/latest/docs/resources/key_prefix) and then another that consumes those values using -[the `consul_keys` data source](/docs/providers/consul/d/keys.html). +[the `consul_keys` data source](https://registry.terraform.io/providers/hashicorp/consul/latest/docs/data-sources/keys). ## Locking and Teamwork diff --git a/website/docs/state/workspaces.html.md b/website/docs/state/workspaces.html.md index 08f26e9bc..358f8e6af 100644 --- a/website/docs/state/workspaces.html.md +++ b/website/docs/state/workspaces.html.md @@ -158,20 +158,20 @@ rather than multiple deployments, data can be passed from one component to another using paired resources types and data sources. For example: * Where a shared [Consul](https://consul.io/) cluster is available, use - [`consul_key_prefix`](/docs/providers/consul/r/key_prefix.html) to - publish to the key/value store and [`consul_keys`](/docs/providers/consul/d/keys.html) + [`consul_key_prefix`](https://registry.terraform.io/providers/hashicorp/consul/latest/docs/resources/key_prefix) to + publish to the key/value store and [`consul_keys`](https://registry.terraform.io/providers/hashicorp/consul/latest/docs/data-sources/keys) to retrieve those values in other configurations. * In systems that support user-defined labels or tags, use a tagging convention to make resources automatically discoverable. For example, use - [the `aws_vpc` resource type](/docs/providers/aws/r/vpc.html) + [the `aws_vpc` resource type](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/vpc) to assign suitable tags and then - [the `aws_vpc` data source](/docs/providers/aws/d/vpc.html) + [the `aws_vpc` data source](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/data-sources/vpc) to query by those tags in other configurations. * For server addresses, use a provider-specific resource to create a DNS record with a predictable name and then either use that name directly or - use [the `dns` provider](/docs/providers/dns/index.html) to retrieve + use [the `dns` provider](https://registry.terraform.io/providers/hashicorp/dns/latest/docs) to retrieve the published addresses in other configurations. * If a Terraform state for one configuration is stored in a remote backend diff --git a/website/intro/use-cases.html.markdown b/website/intro/use-cases.html.markdown index 0c545cf59..e2d3f26fd 100644 --- a/website/intro/use-cases.html.markdown +++ b/website/intro/use-cases.html.markdown @@ -91,7 +91,7 @@ This configuration can then be used by Terraform to automatically setup and modi settings by interfacing with the control layer. This allows configuration to be versioned and changes to be automated. As an example, [AWS VPC](https://aws.amazon.com/vpc/) is one of the most commonly used SDN implementations, and [can be configured by -Terraform](/docs/providers/aws/r/vpc.html). +Terraform](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/vpc). ## Resource Schedulers