Yeah. progress is killing me today. Every Single Step Hurts.

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

tsc

, c) automation locally with

ts-node

. Yet not in azure pipelines with either

tsc

or

ts-node

. And yes - if there was an alternative I could use I would.

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.