Martin Atkins 0b07c5094e planning: Decide the effective replace order for all objects ...

The first pass in the planning engine decides what we're now calling the
"initial replace order" for each object, which can either be
replaceAnyOrder or replaceCreateThenDestroy based purely on whether that
object was configured with "create_before_destroy = true" or not.

The second pass then analyses the materialized graph of resource instance
objects to translate any replaceAnyOrder objects into either
replaceDestroyThenCreate or replaceCreateThenDestroy depending on whether
they are in any dependency chain with something else that requires
replaceCreateThenDestroy.

For now we don't use the results of this for anything, but in a future
commit we'll use it to select the appropriate ordering for the apply-time
operations in the execution graph.

Signed-off-by: Martin Atkins <mart@degeneration.co.uk>

2026-02-23 10:25:42 -08:00

927 B

Raw Blame History

View Raw