Martin Atkins 4cffff24b1 core: Report reason for deferring data read until apply ... We have two different reasons why a data resource might be read only during apply, rather than during planning as usual: the configuration contains unknown values, or the data resource as a whole depends on a managed resource which itself has a change pending. However, we didn't previously distinguish these two in a way that allowed the UI to describe the difference, and so we confusingly reported both as "config refers to values not yet known", which in turn led to a number of reasonable questions about why Terraform was claiming that but then immediately below showing the configuration entirely known. Now we'll use our existing "ActionReason" mechanism to tell the UI layer which of the two reasons applies to a particular data resource instance. The "dependency pending" situation tends to happen in conjunction with "config unknown", so we'll prefer to refer that the configuration is unknown if both are true.		2022-05-09 11:12:47 -07:00
..
diagnostic_test.go	update to use typed sensitive marks	2021-06-25 12:49:07 -04:00
diagnostic.go	command/views/json: Never generate invalid diagnostic snippet offsets	2021-06-28 13:42:28 -07:00
diff_test.go	core: Report reason for deferring data read until apply	2022-05-09 11:12:47 -07:00
diff.go	core: Report reason for deferring data read until apply	2022-05-09 11:12:47 -07:00
difflanguage_string.go	cli: Refactor resource drift rendering	2021-09-16 15:22:37 -04:00
format.go	Move command/ to internal/command/	2021-05-17 14:09:07 -07:00
object_id_test.go	unmark object ID or Name for formatting	2021-08-17 12:24:43 -04:00
object_id.go	unmark object ID or Name for formatting	2021-08-17 12:24:43 -04:00
state_test.go	Move terraform/ to internal/terraform/	2021-05-17 14:09:07 -07:00
state.go	Move terraform/ to internal/terraform/	2021-05-17 14:09:07 -07:00
trivia.go	Move command/ to internal/command/	2021-05-17 14:09:07 -07:00