mirror of https://github.com/pulumi/pulumi.git
4169755866
Similar to destroy --continue-on-error, this flag allows `pulumi up` to continue if any errors are encountered. Currently when we encounter an error while creating/updating a resource, we cancel the context of the deployment executor, and thus the deployment stops once the resources that are being processed in parallel with the failed one finish being updated. For --continue-on-error, we ignore these errors, and let the deployment executor continue. In order for the deployment executor to exit eventually we also have to mark these steps as done, as the deployment executor will otherwise just hang, and callers with open channels waiting for it to finish/report back will hang indefinitely. The errors in the step will still be reported back to the user by the OnResourceStepPost callback. Fixes https://github.com/pulumi/pulumi/issues/14515 --------- Co-authored-by: Fraser Waters <fraser@pulumi.com> |
||
|---|---|---|
| .. | ||
| l1-empty | ||
| l1-main | ||
| l1-output-array | ||
| l1-output-bool | ||
| l1-output-number | ||
| l1-output-string | ||
| l1-stack-reference | ||
| l2-destroy | ||
| l2-engine-update-options | ||
| l2-failed-create-continue-on-error | ||
| l2-resource-simple | ||
| l2-target-up-with-new-dependency | ||
| snapshots | ||
| snapshots_bad | ||
| snapshots_edit | ||
| snapshots_runtime_options/projects/l1-empty | ||