jprdonnelly/opentf
1
0
Fork 0
mirror of https://github.com/opentffoundation/opentf.git synced 2025-12-25 01:00:16 -05:00
Code Issues Packages Projects Releases Wiki Activity

Change docs links: /opentf-> /docs (#367)

Browse Source 
Signed-off-by: Roman Grinovski <roman.grinovski@gmail.com>
This commit is contained in:
Roman Grinovski
2023-09-15 14:10:27 +02:00
committed by GitHub
parent bb1783c63b
commit a4f9c63288
235 changed files with 974 additions and 974 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
website/docs/language/meta-arguments/lifecycle.mdx
View File

@@ -7,7 +7,7 @@ description: >-
# The `lifecycle` Meta-Argument
The [Resource Behavior](/opentf/language/resources/behavior) page describes the general lifecycle for resources. Some details of
The [Resource Behavior](/docs/language/resources/behavior) page describes the general lifecycle for resources. Some details of
that behavior can be customized using the special nested `lifecycle` block
within a resource block body:
@@ -147,7 +147,7 @@ The arguments available within a `lifecycle` block are `create_before_destroy`,
}
```
`replace_triggered_by` allows only resource addresses because the decision is based on the planned actions for all of the given resources. Plain values such as local values or input variables do not have planned actions of their own, but you can treat them with a resource-like lifecycle by using them with [the `terraform_data` resource type](/opentf/language/resources/tf-data).
`replace_triggered_by` allows only resource addresses because the decision is based on the planned actions for all of the given resources. Plain values such as local values or input variables do not have planned actions of their own, but you can treat them with a resource-like lifecycle by using them with [the `terraform_data` resource type](/docs/language/resources/tf-data).
## Custom Condition Checks
@@ -171,7 +171,7 @@ resource "aws_instance" "example" {
Custom conditions can help capture assumptions, helping future maintainers understand the configuration design and intent. They also return useful information about errors earlier and in context, helping consumers more easily diagnose issues in their configurations.
Refer to [Custom Conditions](/opentf/language/expressions/custom-conditions#preconditions-and-postconditions) for more details.
Refer to [Custom Conditions](/docs/language/expressions/custom-conditions#preconditions-and-postconditions) for more details.
## Literal Values Only