pulumi/sdk/nodejs/runtime
Thomas Gummerer 4169755866
Implement up --continue-on-error (#15740)
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>
2024-04-22 11:12:45 +00:00
..
closure Vendor TypeScript and ts-node (#15622) 2024-04-10 15:26:37 +00:00
asyncIterableUtil.ts Apply autoformat 2023-04-28 18:27:10 -04:00
callbacks.ts NodeJS transforms (#15532) 2024-03-07 08:52:34 +00:00
config.ts Apply autoformat 2023-04-28 18:27:10 -04:00
debuggable.ts Use existing PULUMI_DEBUG_PROMISE_LEAKS=1 flag to enable printing 2023-06-15 07:43:05 -07:00
index.ts Add support for async mocks in TS 2023-06-01 13:58:53 +02:00
invoke.ts Cleanup so uses of `any` in the nodejs sdk (#15558) 2024-03-02 00:00:57 +00:00
mocks.ts Export automation.tag.TagMap type & @param tag fixes (#15774) 2024-03-25 14:33:15 +00:00
resource.ts Implement up --continue-on-error (#15740) 2024-04-22 11:12:45 +00:00
rpc.ts Implement up --continue-on-error (#15740) 2024-04-22 11:12:45 +00:00
settings.ts Remove stray console.log (#15616) 2024-03-07 11:21:48 +00:00
stack.ts Export automation.tag.TagMap type & @param tag fixes (#15774) 2024-03-25 14:33:15 +00:00
state.ts NodeJS transforms (#15532) 2024-03-07 08:52:34 +00:00