mirror of
https://github.com/opentofu/opentofu.git
synced 2024-12-30 10:47:14 -06:00
4cffff24b1
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. |
||
|---|---|---|
| .. | ||
| internal/planproto | ||
| objchange | ||
| planfile | ||
| action_string.go | ||
| action.go | ||
| changes_src.go | ||
| changes_state.go | ||
| changes_sync.go | ||
| changes_test.go | ||
| changes.go | ||
| conditions.go | ||
| doc.go | ||
| dynamic_value.go | ||
| mode_string.go | ||
| mode.go | ||
| plan_test.go | ||
| plan.go | ||
| resourceinstancechangeactionreason_string.go | ||