lifecycle m-a ref draft

Author: trujillo-adam

content/terraform/v1.13.x/docs/language/block/data.mdx

@@ -162,12 +162,8 @@ You can specify the following lifecycle rules to manage how Terraform performs o
 
 Configurations defined in the `lifecycle` block affect how Terraform constructs and traverses the dependency graph. You can only use literal values in the lifecycle block because Terraform processes them before it evaluates arbitrary expressions for a run.
 
-The `lifecycle` block is a meta-argument. Meta-arguments are built-in arguments that control how Terraform creates data sources. Refer to [Meta-arguments](/terraform/language/meta-arguments) for more information.
+`lifecycle` is a **meta-argument**. Meta-arguments are built into the Terraform language and control how Terraform creates resources. Refer to the [`lifecycle` reference](/terraform/language/meta-arguments/lifecycle) for details about how the argument works.
 
-#### Summary
-
-- Data type: Block.
-- Default: None.
 
 ### `precondition`
 
@@ -184,26 +180,7 @@ resource {
 }
 ```
 
-The following arguments in the `precondition` block are required:
-
-| Argument | Description | Data type |
-| --- | --- | --- |
-| `condition` | Expression that must return `true` for Terraform to proceed with an operation. You can refer to any other object in the same configuration scope unless the reference creates a cyclic dependency. | Expression that can include references, strings, and operators. |
-| `error_message` | Message that Terraform prints to the console if the `condition` returns `false`. | String |
-
-Terraform evaluates `precondition` blocks before evaluating the resource's configuration arguments. The `precondition` can take precedence over argument evaluation errors.
-
-Terraform evaluates precondition blocks after evaluating [`count`](#count) and [`for_each`](#for_each) meta-arguments. As a result, Terraform can evaluate the `precondition` separately for each instance and makes the `each.key` and `count.index` objects available in the conditions.
-
-You can include a `precondition` and [`postcondition` block](#postcondition) in the same resource. Do not add `precondition` blocks to a `resource` block and a `data` block that represent the same object in the same configuration. Doing so may cause Terraform to ignore changes to the `data` block that result from changes in the `resource` block.
-
-Refer to [Validate your configuration](/terraform/language/validate) for information about adding validations to your Terraform configuration.
-
- #### Summary
-
-- Data type: Block.
-- Default: None.
-- Example: [Apply custom conditions](#apply-custom-conditions).
+`precondition` is a directive available in the `lifecycle` **meta-argument**. Meta-arguments are built into the Terraform language and control how Terraform creates resources. Refer to the [`lifecycle` reference](/terraform/language/meta-arguments/lifecycle) for details about how the argument works.
 
 ### `postcondition`
 
@@ -220,83 +197,4 @@ data "<TYPE>" "<LABEL>" {
 }
 ```
 
-The following arguments in the `precondition` block are required:
-
-| Argument | Description | Data type |
-| --- | --- | --- |
-| `condition` | Expression that must return `true` for Terraform to perform operations on downstream resources. You can refer to any other object in the same configuration scope unless the reference creates a cyclic dependency. | Expression that can include references, strings, and operators. |
-| `error_message` | Message that Terraform prints to the console if the `condition` returns `false`. | String |
-
-Terraform evaluates `postcondition` blocks after planning and applying changes to the data source. Postcondition failures prevent changes to other resources that depend on the failing resource.
-
-You can include a `postcondition` and [`precondition` block](#precondition) in the same resource. Do not add `postcondition` blocks to a `resource` block and a `data` block that represent the same object in the same configuration. Doing so may cause Terraform to ignore changes to the `data` block that result from changes in the `resource` block.
-
-Refer to [Validate your configuration](/terraform/language/validate) for information about adding validations to your Terraform configuration.
-
-#### Summary
-
-- Data type: Block.
-- Default: None.
-- Example: [Apply custom conditions](#apply-custom-conditions).
-
-## Examples
-
-The following examples show how to write configuration for common use cases.
-
-### Apply custom conditions
-
-The following example includes several configurations that illustrate how to define `precondition` and `postcondition` arguments in the `lifecycle` meta-argument.
-
-The following `data` block instructs Terraform to retrieve the ID of the `ami-abc123` AMI:
-
-```hcl
-data "aws_ami" "example" {
-  owners = ["amazon"]
-  filter {
-    name   = "image-id"
-    values = ["ami-abc123"]
-  }
-}
-```
-
-In the following code, the `precondition` block specifies that the AMI ID retrieved from the `data` block must include `x86_64` as its `architecture` attribute. The `postcondition` block specifies that the EC2 instance must be allocated a public DNS hostname. When either condition is not met, Terraform returns the `error_message` for the failed condition:
-
-```hcl
-resource "aws_instance" "example" {
-  instance_type = "t3.micro"
-  ami           = data.aws_ami.example.id
-
-  lifecycle {
-    precondition {
-      condition     = data.aws_ami.example.architecture == "x86_64"
-      error_message = "The selected AMI must be for the x86_64 architecture."
-    }
-
-    postcondition {
-      condition     = self.public_dns != ""
-      error_message = "EC2 instance must be in a VPC that has public DNS hostnames enabled."
-    }
-  }
-}
-```
-
-The following `data` block retrieves the root storage volume connected to the `aws_instance.example` EC2 instance using the `volume_id` attribute. When a `data` resource verifies the result of a managed resource declared in the same configuration, you must define the check in a `postcondition` block in the resource so that Terraform waits for changes to the managed resource to complete before reading the data resource.
-
-```hcl
-data "aws_ebs_volume" "example" {
-  filter {
-    name = "volume-id"
-    values = [aws_instance.example.root_block_device[0].volume_id]
-  }
-  lifecycle {
-    # The EC2 instance will have an encrypted root volume.
-    postcondition {
-      condition     = self.encrypted
-      error_message = "The server's root volume is not encrypted."
-    }
-  }
-}
-output "api_base_url" {
-  value = "https://${aws_instance.example.private_dns}:8433/"
-}
-```
+`postcondition` is a directive available in the `lifecycle` **meta-argument**. Meta-arguments are built into the Terraform language and control how Terraform creates resources. Refer to the [`lifecycle` reference](/terraform/language/meta-arguments/lifecycle) for details about how the argument works.

content/terraform/v1.13.x/docs/language/block/ephemeral.mdx

@@ -223,12 +223,7 @@ You can specify the following lifecycle rules to manage how Terraform performs o
 
 You can include both `precondition` and `postcondition` blocks in the same `lifecycle` block, and you can define multiple `precondition` and `postcondition` blocks in the same `lifecycle` block.
 
-The `lifecycle` 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 more information.
-
-#### Summary
-
-- Data type: Block
-- Default: None
+`lifecycle` is a **meta-argument**. Meta-arguments are built into the Terraform language and control how Terraform creates resources. Refer to the [`lifecycle` reference](/terraform/language/meta-arguments/lifecycle) for details about how the argument works.
 
 ### `precondition`
 
@@ -245,26 +240,7 @@ ephemeral "<TYPE>" "<LABEL>" {
 }
 ```
 
-The following arguments in the `precondition` block are required:
-
-| Argument | Description | Data type |
-| --- | --- | --- |
-| `condition` | Expression that must return `true` for Terraform to proceed with an operation. You can refer to any other object in the same configuration scope unless the reference creates a cyclic dependency. | Expression that can include references, strings, and operators. |
-| `error_message` | Message that Terraform prints to the console if the `condition` returns `false`. | String |
-
-Terraform evaluates `precondition` blocks before evaluating the ephemeral resource's configuration arguments. The `precondition` block errors can take precedence over argument evaluation errors.
-
-Terraform evaluates precondition blocks after evaluating `count` and `for_each` meta-arguments. As a result, Terraform can evaluate the `precondition` separately for each instance and makes the `each.key` and `count.index` objects available in the conditions.
-
-You can include a `precondition` and [`postcondition` block](#postcondition) in the same ephemeral resource.
-
-Refer to [Test and validate](/terraform/language/validate) for information about adding validations to your Terraform configuration.
-
-#### Summary
-
-- Data type: Block
-- Default: None
-- Example: [Validate ephemeral resources](#validate-ephemeral-resources)
+`precondition` is a directive available in the `lifecycle` **meta-argument**. Meta-arguments are built into the Terraform language and control how Terraform creates resources. Refer to the [`lifecycle` reference](/terraform/language/meta-arguments/lifecycle) for details about how the argument works.
 
 ### `postcondition`
 
@@ -281,24 +257,7 @@ ephemeral "<TYPE>" "<LABEL>" {
 }
 ```
 
-The following arguments in the `postcondition` block are required:
-
-| Argument | Description | Data type |
-| --- | --- | --- |
-| `condition` | Expression that must return `true` for Terraform to perform operations on downstream resources. You can refer to any other object in the same configuration scope unless the reference creates a cyclic dependency. | Expression that can include references, strings, and operators. |
-| `error_message` | Message that Terraform prints to the console if the `condition` returns `false`. | String |
-
-Terraform evaluates `postcondition` blocks after planning and applying changes to the ephemeral resource. Postcondition failures prevent changes to other resources that depend on the failing ephemeral resource.
-
-You can include a `postcondition` and [`precondition` block](#precondition) in the same ephemeral resource.
-
-Refer to [Test and validate](/terraform/language/validate) for information about adding validations to your Terraform configuration.
-
-#### Summary
-
-- Data type: Block
-- Default: None
-- Example: [Validate ephemeral resources](#validate-ephemeral-resources)
+`postcondition` is a directive available in the `lifecycle` **meta-argument**. Meta-arguments are built into the Terraform language and control how Terraform creates resources. Refer to the [`lifecycle` reference](/terraform/language/meta-arguments/lifecycle) for details about how the argument works.
 
 ## Examples
 
@@ -363,42 +322,4 @@ resource "aws_db_instance" "example" {
 
 Neither write-only arguments nor `ephemeral` resources are persisted outside of the current Terraform run, ensuring that the `ephemeral.random_password.db_password.result` value is completely omitted from state and plan files.
 
-Terraform does not store the generated value of `ephemeral.random_password.db_password.result`, but you can capture it in another resource to ensure the value is not lost. For an example of generating, storing, retrieving, and using an ephemeral password, refer to [write-only arguments](/terraform/language/manage-sensitive-data/write-only#set-and-store-an-ephemeral-password-in-aws-secrets-manager).
-
-
-### Validate ephemeral resources
-
-In the following example, the `aws_ssm_parameter` ephemeral resource has a precondition to ensure that compliance mode is enabled to secure production secrets, and a postcondition to ensure the generated password meets password requirements:
-
-<CodeBlockConfig highlight="15-25">
-
-```hcl
-variable "environment" {
-  description = "Deployment environment"
-  type        = string
-}
-
-variable "compliance_mode" {
-  description = "Enable compliance requirements for production"
-  type        = bool
-  default     = false
-}
-
-ephemeral "aws_ssm_parameter" "database_password" {
-  name = "/secrets/${var.environment}/database/password"
-
-  lifecycle {
-    precondition {
-      condition     = var.environment != "prod" || var.compliance_mode == true
-      error_message = "Enable compliance mode to assess production secrets."
-    }
-
-    postcondition {
-      condition     = can(regex("^[A-Za-z0-9!@#$%^&*()_+=-]{16,}$", self.value))
-      error_message = "Password from external source must meet security requirements."
-    }
-  }
-}
-```
-
-</CodeBlockConfig>
+Terraform does not store the generated value of `ephemeral.random_password.db_password.result`, but you can capture it in another resource to ensure the value is not lost. For an example of generating, storing, retrieving, and using an ephemeral password, refer to [write-only arguments](/terraform/language/manage-sensitive-data/write-only#set-and-store-an-ephemeral-password-in-aws-secrets-manager).