mirror of
https://github.com/hashicorp/terraform.git
synced 2026-02-18 18:29:44 -05:00
docs: Explicitly mention states should not contain unknown values (#34491)
Reference: https://github.com/hashicorp/terraform-plugin-testing/issues/262 This is a quick documentation update to the Resource Instance Change Lifecycle page to explicitly call out that unknown values are never permitted in any resource instance state.
This commit is contained in:
parent
a9b43f332e
commit
7958dc1e77
1 changed files with 3 additions and 1 deletions
|
|
@ -247,6 +247,8 @@ information as the **Previous Run State** but does so in a way that conforms
|
|||
to the current version of the resource type schema, which therefore allows
|
||||
Terraform Core to interact with the data fully for subsequent steps.
|
||||
|
||||
No unknown values are permitted in the **Updated State**.
|
||||
|
||||
### ReadResource
|
||||
|
||||
Although Terraform typically expects to have exclusive control over any remote
|
||||
|
|
@ -289,7 +291,7 @@ following two situations for each attribute:
|
|||
|
||||
This operation returns the **Prior State** to use for the next call to
|
||||
`PlanResourceChange`, thus completing the circle and beginning this process
|
||||
over again.
|
||||
over again. No unknown values are permitted in the **Prior State**.
|
||||
|
||||
## Handling of Nested Blocks in Configuration
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue