sparse-intern-71089
09/17/2021, 11:41 PMlemon-agent-27707
09/20/2021, 2:23 PM@pulumi/pulumi
and related packages you're using (maybe share package.json)lemon-agent-27707
09/20/2021, 2:24 PMplain-dawn-65221
09/20/2021, 7:53 PMpackage.json
for the small sample above is attached.
Using:
• @pulumi/aws
4.20.0
• @pulumi/pulumi
3.12.0
plain-dawn-65221
09/20/2021, 7:56 PMstack.up()
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 stack.up()
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 stack.up()
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 stack.up()
returns to functioning properly on the other stacksplain-dawn-65221
09/20/2021, 8:00 PMstack.up()
are causing wide-ranging problems in our use case, and we're wondering what the best way to catch and handle stack.up()
errors areplain-dawn-65221
09/20/2021, 8:01 PMlemon-agent-27707
09/20/2021, 8:21 PMlemon-agent-27707
09/20/2021, 8:22 PMplain-dawn-65221
09/21/2021, 2:01 PMstack.up()
operations are sequential ("serial")plain-dawn-65221
09/21/2021, 2:02 PMplain-dawn-65221
09/21/2021, 8:06 PMtry
catch
in as many places as I could think to in the main.js
file above ^
The error output still shows UnhandledPromiseRejectionWarnings
To phrase my original question better:
• What promise isn't being handled? Is it in the main.js
file somewhere or somewhere in Pulumi SDK?lemon-agent-27707
09/22/2021, 2:18 AMred-match-15116
09/22/2021, 2:47 AMWhat 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?main.js
plain-dawn-65221
09/22/2021, 3:37 AMproud-pizza-80589
10/12/2021, 2:49 PM