Skip to content

Commit d6c8b06

Browse files
authored
docs: Add more clarification for unknown values during config validation (#1023)
1 parent 0f21b14 commit d6c8b06

File tree

1 file changed

+7
-2
lines changed

1 file changed

+7
-2
lines changed

website/docs/plugin/framework/handling-data/terraform-concepts.mdx

+7-2
Original file line numberDiff line numberDiff line change
@@ -119,5 +119,10 @@ value. However, by the time a resource is expected to be created, read, updated,
119119
deleted, only its computed attributes can be unknown. The rest are
120120
guaranteed to have known values (or be null).
121121

122-
Provider configuration values can be unknown, and providers should handle that
123-
situation, even if that means just returning an error.
122+
For concepts such as resource and data source [configuration validation](/terraform/plugin/framework/validation),
123+
this means that Terraform guarantees to call validation for a non-computed attribute
124+
eventually with a known value, so the provider should typically avoid returning error diagnostics
125+
when encountering an unknown value during validation.
126+
127+
Provider configuration values [can also be unknown](/terraform/plugin/framework/providers#unknown-values), and
128+
providers should handle that situation, even if that means just returning an error.

0 commit comments

Comments
 (0)