From 7958dc1e773f2ef7db9f34e8bfc8cb296efe39f2 Mon Sep 17 00:00:00 2001 From: Brian Flad Date: Thu, 25 Jan 2024 15:17:29 +0100 Subject: [PATCH] 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. --- docs/resource-instance-change-lifecycle.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/resource-instance-change-lifecycle.md b/docs/resource-instance-change-lifecycle.md index 08e5ae390b..2c1b59c094 100644 --- a/docs/resource-instance-change-lifecycle.md +++ b/docs/resource-instance-change-lifecycle.md @@ -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