dazzling-scientist-8082605/14/2019, 9:03 PM
It definitely is the second case: a cyclic dependency, but I’m not sure how to break the cycle. I’ve got a lambda that closes over a function that constructs a config/context object sort of thing, but another lambda that needs the arn of that first lambda - is there some general trick to break the cycle in this sort of situation?
The Pulumi runtime detected that 114 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
and then at the bottom fo the file
where … includes some code that needs the arn of the lambda f
newContext = ...
creamy-potato-2940205/15/2019, 7:23 PM
bitter-oil-4608105/15/2019, 7:28 PM
you see the value that you end up defining later in the file? I think that the pattern of doing a let to initialize a variable, capturing that, and then latter assigning to it in the deployment program is going to lead to racy behavior since you don't have control over when the lambda which captured newContext is serialized.