most-lighter-95902
01/13/2022, 12:59 AMlemon-agent-27707
01/13/2022, 2:58 AMaws:skipMetadataApiCheck false
most-lighter-95902
01/13/2022, 3:34 AMres.json({ success: true})
from my express server, it returns fine, but when using Pulumi Automation, I get upstream request timeout
as a response with 504 error code even though the stack update has been completed successfully.const upRes = await stack.up({ onOutput: <http://console.info|console.info> })
console.log('stack upRes', upRes)
res.json({
outputs: upRes.outputs,
})
upstream request timeout
lemon-agent-27707
01/13/2022, 5:26 AMmost-lighter-95902
01/13/2022, 5:58 AMlemon-agent-27707
01/14/2022, 12:31 AMmost-lighter-95902
01/14/2022, 12:40 AMupRest.outputs
, return values inside it? I’ll try thatstack.up().then(upRes => // do something with upRes here))
) and then the server crashes (or I do another push and it restarts) mid-process, will the then
still run?await stack.outputs()
) to check the status instead? Does it even return the status?lemon-agent-27707
01/14/2022, 7:44 PMthen
will not run.
Generally it is best to avoid canceling inflight updates. It can leave dangling resources and inconsistencies in your state file. You can cancel
a stack, and remove any pending operations by running export
and import
and then refreshing the stack to get the latest state of resources.
My recommendation would be to architect your system in such a way that updates can run to completion even when you do a deployment. A queue/worker might make it easier to enable this.most-lighter-95902
01/15/2022, 5:38 AM