forport meta-args topics to 1.14 core - TODO stacks

Author: trujillo-adam

content/terraform/v1.14.x (beta)/data/language-nav-data.json

@@ -389,7 +389,37 @@
   },
   {
     "title": "Meta-arguments",
-    "path": "meta-arguments"
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "meta-arguments",
+        "alias": "actions"
+      },
+      {
+        "title": "count",
+        "path": "meta-arguments/count"
+      },
+      {
+        "title": "depends_on",
+        "path": "meta-arguments/depends_on"
+      },
+      {
+        "title": "for_each",
+        "path": "meta-arguments/for_each"
+      },
+      {
+        "title": "lifecycle",
+        "path": "meta-arguments/lifecycle"
+      },
+      {
+        "title": "provider",
+        "path": "meta-arguments/provider"
+      },
+      {
+        "title": "providers",
+        "path": "meta-arguments/providers"
+      }
+    ]
   },
   {
     "title": "Built-in resources",

content/terraform/v1.14.x (beta)/docs/language/block/action.mdx

@@ -14,8 +14,8 @@ The `action` block supports the following configuration:
 - [`action "<TYPE>" "<LABEL>"`](#action) &nbsp block
    - [`config`](#config) &nbsp; map of arguments or nested blocks
       - [`PROVIDER ARGUMENTS`](#config)
-  - [`for_each`](#for_each) &nbsp; map or set of strings | mutually exclusive with `count`
   - [`count`](#count) &nbsp; number | mutually exclusive with `for_each`
+  - [`for_each`](#for_each) &nbsp; map or set of strings | mutually exclusive with `count`
   - [`provider`](#provider) &nbsp; reference 
 
 ## Complete configuration
@@ -72,6 +72,18 @@ The `config` block may contain arguments, nested blocks, or a combination of bot
 - Data type: Map of arguments or nested blocks
 - Example: [Define an action](#define-an-action)
 
+### `count`
+
+The `count` meta-argument instructs Terraform to invoke an action multiple times using the same configuration.
+
+```hcl
+resource {
+  count = <number>
+}
+```
+
+`count` is a **meta-argument**. Meta-arguments are built into the Terraform language and control how Terraform creates resources. Refer to the [`count` reference](/terraform/language/meta-arguments/count) for details about how the argument works.
+
 ### `for_each` 
 
 The `for_each` meta-argument instructs Terraform to invoke the action once for each member of a list or key-value pair in a map.
@@ -103,67 +115,7 @@ action "<TYPE>" "<LABEL>" {
 
 </Tabs>
 
-The `for_each` meta-argument accepts a map or a set of strings and invokes the action once for each item in that map or set. Each invocation is associated with a distinct infrastructure object. 
-
-You can use pure functions, such as `toset()` and `tomap()`, to create a map or set for use in the `for_each` argument. All values must be known when Terraform plans your action, whether iterating over the keys of a map or set of strings. Otherwise, Terraform prints an error message that `for_each` has dependencies that it cannot determine before applying the configuration.
-
-Keys in the `for_each` argument cannot be the result of or rely on the result of impure functions, such as `uuid`, `bcrypt`, or `timestamp`, because Terraform defers evaluating impure functions during the main evaluation step.
-
-The `for_each` argument does not implicitly convert lists or tuples to sets. To declare resource instances based on a nested data structure or combinations of elements from multiple data structures, you can use Terraform expressions and functions to derive a suitable value. Refer to the following examples for more information:
-
-- [Transform a multi-level nested structure into a flat list](/terraform/language/functions/flatten#flattening-nested-structures-for-for_each).
-- [Combine collections to produce a list of element combinations](/terraform/language/functions/setproduct#finding-combinations-for-for_each).
-
-You cannot use sensitive values, such as [sensitive input variables](/terraform/language/block/variable#sensitive), [sensitive outputs](/terraform/language/block/output#sensitive), or [sensitive resource attributes](/terraform/language/expressions/references#sensitive-resource-attributes), as arguments in `for_each`. Because Terraform uses the value in `for_each` to identify the action instance and always discloses it in UI output, sensitive values are not allowed. Terraform returns an error if you attempt to use sensitive values as `for_each` arguments.
-
-If you transform a value containing sensitive data into an argument for use in `for_each`, be aware that most functions in Terraform will return a sensitive result if given an argument with sensitive content. In many cases, you can achieve similar results with a `for` expression. For example, to call `keys(local.map)` where `local.map` is an object with sensitive values, but non-sensitive keys, you can create a value to pass to `for_each` using `toset([for k,v in local.map : k])`.
-
-Refer to [Manage sensitive data](/terraform/language/manage-sensitive-data) for more information.
-
-The `for_each` argument exposes an `each` object that you can reference within the same block to modify specific instances of the action. The object has the following attributes:
-
-- `each.key`: Map key or list member that corresponds to an instance.
-- `each.value`: Map value that corresponds to an instance.
-
-Use the `<TYPE>.<NAME>[<KEY>]` syntax to access an instance of a resource created using `for_each`. For example, `aws_lambda_invoke.server["a_group"]` refers to an invocation of the `aws_lambda_invoke` action named `server` from a key named `a_group`.
-
-The `for_each` argument is a meta-argument, which is built into Terraform and controls the way that Terraform creates resources. Refer to [Meta-arguments](/terraform/language/meta-arguments) for more information.
-
-#### Summary
-
-- Data type: Map or set of strings.
-- Default: None.
-- Example: [Invoke an action multiple times](#invoke-an-action-multiple-times).
-
-### `count`
-
-The `count` meta-argument instructs Terraform to invoke an action multiple times using the same configuration.
-
-```hcl
-resource {
-  count = <number>
-}
-```
-
-The value must be a whole number. You can reference variables or local values and use expressions to compute the value, but the value must resolve to a whole number.
-
-In blocks where `count` is set, Terraform exposes an additional `count` object. You can reference the object to modify the configuration of each invocation. The `count` object has an `index` attribute starting from `0`.
-
-To refer to an individual instance of an invocation using the `count` meta-argument, use the `<TYPE>.<NAME>[INDEX]` syntax. For example, `aws_lambda_invoke.server[0]` refers to the first invocation of the `aws_lambda_invoke` action named `server`.
-
-<Tip>
-
-You can use the `count` argument as a conditional. For example, setting a `count = var.creator ? 3 : 0` instructs Terraform to invoke an action three times when a variable named `creator` is set to `true`. When `creator` is set to `false`, Terraform does not invoke the action. Refer to [​​Conditional Expressions](/terraform/language/expressions/conditionals) for more information.
-
-</Tip>
-
-The `count` argument is a meta-argument, which is built into Terraform and controls the way that Terraform creates resources. Refer to [Meta-arguments](/terraform/language/meta-arguments) for more information.
-
-#### Summary
-
-- Data type: Number.
-- Default: None.
-- Example: [Invoke an action multiple times](#invoke-an-action-multiple-times).
+`for_each` is a **meta-argument**. Meta-arguments are built into the Terraform language and control how Terraform creates resources. Refer to the [`for_each` reference](/terraform/language/meta-arguments/for_each) for details about how the argument works.
 
 ### `provider`
 
@@ -175,17 +127,7 @@ action "<TYPE>" "<LABEL>" {
 }
 ```
 
-By default, Terraform automatically selects a provider based on the action type, but you can create multiple provider configurations and use a non-default configuration for specific actions.
-
-Use the `<PROVIDER>.<ALIAS>` syntax to reference a provider configuration in the `provider` argument.
-
-The `provider` argument is a meta-argument, which is built into Terraform and controls the way that Terraform creates resources. Refer to [Meta-arguments](/terraform/language/meta-arguments) for more information.
-
-#### Summary
-
-- Data type: Reference.
-- Default: None.
-- Example: [Select an alternate provider configuration](#select-an-alternate-provider-configuration).
+`provider` is a **meta-argument**. Meta-arguments are built into the Terraform language and control how Terraform creates resources. Refer to the [`provider` reference](/terraform/language/meta-arguments/provider) for details about how the argument works.
 
 ## Examples
 

content/terraform/v1.14.x (beta)/docs/language/block/check.mdx

@@ -122,7 +122,7 @@ The arguments within a `data` block are provider-specific. Refer to the [registr
 
 ### `depends_on`
 
-The `depends_on` argument specifies an upstream resource that the `data` block depends on. Terraform must complete all operations on the upstream resource before fetching information from the `data` block.
+The `depends_on` argument specifies an upstream resource that the `data` block depends on. Terraform must complete all operations on the upstream resource before fetching information from the `data` block. 
 
 ```hcl
 check "unique_name" {
@@ -135,13 +135,7 @@ check "unique_name" {
 }
 ```
 
-We recommend adding the `depends_on` argument if your nested data source depends on another resource without referencing that resource directly.
-
-For example, if you define a `check` that verifies that a website API returns `200`, that check fails the first time Terraform runs your configuration because your website's infrastructure does not exist yet. You can set the `depends_on` argument to a resource, such as the load balancer, to ensure Terraform only runs the `check` once the website is up. When running an operation, Terraform evaluates the `check`, warns `known after apply` until that crucial piece of your website is ready, and continues the operation.
-
-However, this strategy only works when the `data` block does not directly reference the resource specified in the `depends_on` argument. Otherwise, anytime that resource changes, the `check` block warns `known after apply` until Terraform updates that resource, making your check potentially noisy and ineffective. Refer to the [example](#resource-dependency) for more details.
-
-The `depends_on` block is a meta-argument. Meta-arguments are built-in arguments that control how Terraform creates resources. Refer to [Meta-arguments](/terraform/language/meta-arguments) for additional information.
+`depends_on` is a **meta-argument**. Meta-arguments are built into the Terraform language and control how Terraform creates resources. Refer to the [`depends_on` reference](/terraform/language/meta-arguments/depends_on) for details about how the argument works.
 
 ### `provider`
 
@@ -158,16 +152,7 @@ check "unique_name" {
 }
 ```
 
-By default, Terraform automatically selects a provider based on the nested data source's type, but you can create multiple provider configurations and use a non-default configuration for specific data sources.
-
-The `provider` argument is a meta-argument, which is built into Terraform and controls the way that Terraform creates resources. Refer to [Meta-arguments](/terraform/language/meta-arguments) for additional information.
-
-#### Summary
-
-- Data type: Block.
-- Default: None.
-- Supported meta-arguments: `depends_on` and `provider`.
-- Example: [Resource dependency](#resource-dependency).
+`provider` is a **meta-argument**. Meta-arguments are built into the Terraform language and control how Terraform creates resources. Refer to the [`provider` reference](/terraform/language/meta-arguments/provider) for details about how the argument works.
 
 ## Examples