pulumi/pkg/resource
Thomas Gummerer 34b0409d07
continue-on-error: respect all dependency relationships (#16639)
When running `pulumi up --continue-on-error`, we can't bring up new
resources that have dependencies that have failed, or have been skipped.
Since the resource would have a failed dependency, that dependency would
not be in the snapshot, resulting in a snapshot integrity failure. Also
it simply does not make sense to `up` a resource that has a failed
dependency.

We took care of that for the regular dependency relationship, however at
the time we missed doing the same for other types of dependencies,
namely parent-child relationships, deleted with relationships and
property dependencies.

This can result in snapshot integrity failures for example when a parent
fails to be created, but we still do the resource creation of the child,
such as what happened in https://github.com/pulumi/pulumi/issues/16638.

Fix this by skipping the step when a resource with any type of
dependency relationship fails or is skipped beforehand.

Fixes https://github.com/pulumi/pulumi/issues/16638
2024-07-12 09:42:57 +00:00
..
analyzer Clean up uses of .Error() (#14965) 2023-12-20 15:54:06 +00:00
deploy continue-on-error: respect all dependency relationships (#16639) 2024-07-12 09:42:57 +00:00
edit Rewrite `DeletedWith` properties when renaming stacks (#16216) 2024-05-16 15:09:32 +00:00
graph state_move: add --include-parents flag (#16628) 2024-07-11 12:59:20 +00:00
provider turn on the golangci-lint exhaustive linter (#15028) 2024-01-17 16:50:41 +00:00
stack implement skeleton command for `pulumi state move` (#16493) 2024-06-28 09:43:19 +00:00
testdata ci: radical idea - what if slow tests & no stdout makes GH consider runner dead? 2022-03-06 14:52:13 -08:00