You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Martin Atkins a50b861420 plans: Retain output value changes for all outputs in memory ... 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.		8 years ago
..
internal/planproto	plans: Record private data bytes as part of resource change	8 years ago
objchange	plans/objchange: Don't panic if old or new values are null	8 years ago
planfile	plans: Retain output value changes for all outputs in memory	8 years ago
action.go	…
action_string.go	…
changes.go	plans: Retain output value changes for all outputs in memory	8 years ago
changes_src.go	plans: Retain output value changes for all outputs in memory	8 years ago
changes_state.go	…
changes_sync.go	plans: Retain output value changes for all outputs in memory	8 years ago
doc.go	…
dynamic_value.go	core: Re-implement EvalWriteDiff to work with new plan types	8 years ago
dynamic_value_test.go	…
plan.go	terraform: Ugly huge change to weave in new State and Plan types	8 years ago
plan_test.go	terraform: Ugly huge change to weave in new State and Plan types	8 years ago