IntenseWebs/opentofu
3
0
Fork 0
mirror of https://github.com/opentofu/opentofu.git synced 2025-01-28 09:26:26 -06:00
Code Issues Packages Projects Releases Wiki Activity

docs: Explicitly mention Computed-only attribute behavior for Proposed New State

Browse Source 
Reference: 21bb677db7/internal/plans/objchange/objchange.go (L289-L292)

Previously, the resource lifecycle documentation for Proposed New State only mentioned special behavior for Optional and Computed attributes. This minor documentation update mentions that Terraform also imposes special behavior on Computed-only attributes (preserving any Prior State value).
This commit is contained in:
Brian Flad 2023-01-10 14:50:02 -05:00
parent 21bb677db7
commit 0b8c65fa4e
No known key found for this signature in database
GPG Key ID: AC40A9A6632E4888
1 changed files with 5 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
docs/resource-instance-change-lifecycle.md
View File

@ -33,9 +33,11 @@ The various object values used in different parts of this process are:
which a provider may use as a starting point for its planning operation.
The built-in logic primarily deals with the expected behavior for attributes
marked in the schema as both "optional" _and_ "computed", which means that
the user may either set it or may leave it unset to allow the provider
to choose a value instead.
marked in the schema as "computed". If an attribute is only "computed",
Terraform expects the value to only be chosen by the provider and it will
preserve any Prior State. If an attribute is marked as "computed" and
"optional", this means that the user may either set it or may leave it
unset to allow the provider to choose a value.
Terraform Core therefore constructs the proposed new state by taking the
attribute value from Configuration if it is non-null, and then using the