02/10/2021, 4:18 PM
The Pulumi runtime detected that 50 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
    Leaving promises active is probably not what you want. If you are unsure about
    why you are seeing this message, re-run your program with the `PULUMI_DEBUG_PROMISE_LEAKS`
    environment variable. The Pulumi runtime will then print out additional
    debug information about the leaked promises.
adding PULUMI_DEBUG_PROMISE_LEAKS doesn’t help at all, I am getting 1000+ messages
I probably know where is the issue, by removing empty promise hack from here (https://pulumi-community.slack.com/archives/C84L4E3N1/p1612887789413700)
it gets working inside
pulumi up
(preview) mode
but I really want to have that functionality, yesterday it was working like a charm
    ? new Promise(() => {}) : new Promise(async (resolve, reject) => ....)
by giving an empty promise, pulumi was skipping resolving next child values
the value will be computed only after it will be deployed and available for read, so there is a
promise that helps me to do that.
by adding resources around this dirty hack
new Promise(() => {})
I got this issue with leak
any suggestions?
// Computed represents the absence of a property value, because it will be computed at some point in the future.  It
// contains a property value which represents the underlying expected type of the eventual property value.
How I can make this computed property from ts?
I’ve created the issue inside pulumi repo