great-sunset-355
01/11/2024, 3:47 PMPULUMI_DEBUG_PROMISE_LEAKS
-> this variable is not very helpful
The Pulumi runtime detected that 468 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.
little-cartoon-10569
01/14/2024, 7:43 PMsteep-portugal-37539
01/26/2024, 6:08 PMawsx.ec2.VPC
resource and then an eks.Cluster
resource. For the parent
option in ResourceOptions
of the cluster, i set the created vpc. Pulumi doesn’t like this and i get the runtime detected promises error
Edit: created an issue: https://github.com/pulumi/pulumi-awsx/issues/1209