terraform/plans
Kristin Laemmert c661157999 plans/objchange: further harden ProposedNewObject against ~weird~
incoming values

Addresses an odd state where the priorV of an object to be changed is
known but null.

While this situation should not happen, it seemed prudent to ensure that
core is resilient to providers sending incorrect values (which might
also occur with manually edited state).
2018-10-16 19:14:11 -07:00
..
internal/planproto core: Handle forced-create_before_destroy during the plan walk 2018-10-16 19:14:11 -07:00
objchange plans/objchange: further harden ProposedNewObject against ~weird~ 2018-10-16 19:14:11 -07:00
planfile core: Fix test build for ./plans/planfile 2018-10-16 19:14:11 -07:00
action.go core: Handle forced-create_before_destroy during the plan walk 2018-10-16 19:14:11 -07:00
action_string.go plans: Regenerate Action.String for new action values 2018-10-16 19:14:11 -07:00
changes.go core: Handle forced-create_before_destroy during the plan walk 2018-10-16 19:14:11 -07:00
changes_src.go plans: Retain output value changes for all outputs in memory 2018-10-16 19:14:11 -07:00
changes_state.go plans: New package for in-memory plan models 2018-10-16 18:50:29 -07:00
changes_sync.go plans: Retain output value changes for all outputs in memory 2018-10-16 19:14:11 -07:00
doc.go plans: New package for in-memory plan models 2018-10-16 18:50:29 -07:00
dynamic_value.go core: Re-implement EvalWriteDiff to work with new plan types 2018-10-16 19:14:11 -07:00
dynamic_value_test.go plans: New package for in-memory plan models 2018-10-16 18:50:29 -07:00
plan.go terraform: Ugly huge change to weave in new State and Plan types 2018-10-16 19:11:09 -07:00
plan_test.go make Changes.Empty() not count NoOps 2018-10-16 19:14:11 -07:00