happy-kitchen-33409
07/12/2023, 5:08 PMthe stack is currently locked by 1 lock(s)
.
We use the automation API, and in some cases the pulumi process is killed (due to timeout etc). So "wait" probably won't work.
For pulumi cancel
, the documentation says "this operation is _very dangerous_". And we've had some leaked resources that I suspect is because of pulumi cancel
(resources exist, but not tracked in the corresponding pulumi stack).
What's the recommended way to solve this problem (ideally automatically, without human interaction)? Thanks!billowy-army-68599
cancel
is the way to deal with locked stacks, but if the process is interrupted you’re going to leak resourceshappy-kitchen-33409
07/12/2023, 5:55 PMbillowy-army-68599
happy-kitchen-33409
07/12/2023, 6:35 PMbillowy-army-68599
salmon-gold-74709
07/12/2023, 9:10 PMhappy-kitchen-33409
07/13/2023, 5:39 PMsalmon-gold-74709
07/13/2023, 5:43 PMhappy-kitchen-33409
07/13/2023, 5:53 PMsalmon-gold-74709
07/13/2023, 5:54 PMhappy-kitchen-33409
07/13/2023, 6:05 PMsalmon-gold-74709
07/13/2023, 6:09 PMhappy-kitchen-33409
07/13/2023, 6:15 PMsalmon-gold-74709
07/13/2023, 6:25 PM