I m seeing some promise leak errors when calling `api addRou Pulumi Community #general

I’m seeing some promise leak errors when calling `...

swift-account-41358

12/16/2024, 8:15 PM

I’m seeing some promise leak errors when calling

api.addRoute()

(TypeScript) When running with PULUMI_DEBUG_PROMISE_LEAKS=1 I see that the stack traces for each are similar but there differences at the end of the trace for each. They are:

Copy code

CONTEXT(9676): transferIsSecret(resource:OmwPsoBeApiRouteDzrksnPermissions[aws:lambda/permission:Permission], functionUrlAuthType, undefined)

CONTEXT(9677): transferDeps(resource:OmwPsoBeApiRouteDzrksnPermissions[aws:lambda/permission:Permission], functionUrlAuthType, undefined)

CONTEXT(9678): transferProperty(resource:OmwPsoBeApiRouteDzrksnPermissions[aws:lambda/permission:Permission], principal, <http://apigateway.amazonaws.com|apigateway.amazonaws.com>)

CONTEXT(9679): transferIsStable(resource:OmwPsoBeApiRouteDzrksnPermissions[aws:lambda/permission:Permission], principal, <http://apigateway.amazonaws.com|apigateway.amazonaws.com>)

Attached is the full stack trace. Any thoughts on what could be causing them?

promise-leak.txt

swift-account-41358

12/16/2024, 8:17 PM

I’m deploying a combination of mostly SST v3 defined components with a few Pulumi constructs to AWS. I’ve asked on the SST Discord too but thought I’d share in case there were some avenues I could be exploring

swift-account-41358

12/17/2024, 9:20 AM

Ok, turns out this was a problem within SST’s implementation of providing privileges for a bucket to a lambda when that lambda was the target of a bucket notification

4 Views

Open in Slack

Previous Next