d53c3d5c1b
During the plan operation we need to retain _somewhere_ the planned changes for all outputs so we can refer to them during expression evaluation. For consistency with how we handle resource instance changes, we'll keep them in the plan so we can properly retain unknown values, which cannot be written to state. As with output values in the state, only root output plans are retained in a round-trip through the on-disk plan file format, but that's okay because we can trivially re-calculate all of these during apply. We include the _root_ outputs in the plan file only because they are externally-visible side effects that ought to be included in any rendering of the plan made from the plan file for user inspection. |
||
|---|---|---|
| .. | ||
| internal/planproto | ||
| objchange | ||
| planfile | ||
| action.go | ||
| action_string.go | ||
| changes.go | ||
| changes_src.go | ||
| changes_state.go | ||
| changes_sync.go | ||
| doc.go | ||
| dynamic_value.go | ||
| dynamic_value_test.go | ||
| plan.go | ||
| plan_test.go | ||