plain-dawn-6522109/17/2021, 11:41 PM
Errors like this result in a large number of
, fills up our logging, and if running in an unattended loop seem to crash the Pulumi runtime
If someone is able to advise on the best approach for handling
errors, we'd appreciate it!
lemon-agent-2770709/20/2021, 2:23 PM
and related packages you're using (maybe share package.json)
plain-dawn-6522109/20/2021, 7:53 PM
for the small sample above is attached.
for each stack, which either applies the changes, or does nothing (if no change requests came in)
It seems like what we are observing is that if a change request comes in for one of the stacks that causes a
error on that one stack, there are cascading effects on the other stacks — our best guess is that the Pulumi runtime is somehow affected
The other "healthy" stacks will run
and output a single generic error at the end that says "one or more errors occurred"
If we delete the single stack that we know has an error, then
returns to functioning properly on the other stacks
are causing wide-ranging problems in our use case, and we're wondering what the best way to catch and handle
lemon-agent-2770709/20/2021, 8:21 PM
plain-dawn-6522109/21/2021, 2:01 PM
operations are sequential ("serial")
in as many places as I could think to in the
file above ^
The error output still shows
To phrase my original question better:
• What promise isn't being handled? Is it in the
file somewhere or somewhere in Pulumi SDK?
lemon-agent-2770709/22/2021, 2:18 AM
red-match-1511609/22/2021, 2:47 AM
What promise isn’t being handled? Is it in theYour code sample appears correct, this seems like an issue within the Pulumi SDKfile somewhere or somewhere in Pulumi SDK?
plain-dawn-6522109/22/2021, 3:37 AM
proud-pizza-8058910/12/2021, 2:49 PM