mirror of https://github.com/pulumi/pulumi.git
34b0409d07
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 |
||
|---|---|---|
| .. | ||
| asset | ||
| authhelpers | ||
| backend | ||
| cmd/pulumi | ||
| codegen | ||
| display | ||
| engine | ||
| graph | ||
| importer | ||
| operations | ||
| resource | ||
| secrets | ||
| testing/integration | ||
| util | ||
| version | ||
| workspace | ||
| README.md | ||
| go.mod | ||
| go.sum | ||
README.md
pulumi/pkg
While pulumi/sdk maintains strict backwards compatibility guarantees, code under pkg/ is handled more informally: while breaking changes are still discouraged they may happen when they make sense.