6fd82ef97e
Since we do our deletes using a separate graph node from all of the other actions, and a "Replace" change implies both a delete _and_ a create, we need to pretend at apply time that a single replace change was actually two separate changes. This will also early-exit eval if a destroy node finds a non-Delete change or if an apply node finds a Delete change. These should not happen in practice because we leave these nodes out of the graph when they are not needed for the given action, but we do this here for robustness so as not to have an invisible dependency between the graph builder and the eval phase. |
||
|---|---|---|
| .. | ||
| 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 | ||