Yeah. progress is killing me today. Every Single S...
# automation-api
Yeah. progress is killing me today. Every Single Step Hurts.
Copy code
Error: The Pulumi runtime detected that 904 promises were still active
at the time that the process exited. There are a few ways that this can occur:
  * Not using `await` or `.then` on a Promise returned from a Pulumi API
  * Introducing a cyclic dependency between two Pulumi Resources
  * A bug in the Pulumi Runtime
This works fine a) with pulumi cli, b) automation locally with
, c) automation locally with
. Yet not in azure pipelines with either
. And yes - if there was an alternative I could use I would.
And if you're wondering, yes, pretty much every reference to every resource is listed in the debug info.
This sounds like a bug, would you mind filing an issue so we can investigate?
Will try to do - but it's also likely that it's because of the way I'm running my stuff. will try to get a reproducable new stack thing going, just running low on networks I can use for testing.
And.. this is weird.. but afaik this is only reproducible when I'm running automation through an azure pipeline 😕 created. It's going to a be a pain to reproduce I fear.. that is - I can reproduce it every time, but it's just a pain to get anything set up with azure pipelines 😄