No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

I have a question about lambda closure serialization. We're using nodejs with pulumi to deploy our lambdas as callback functions (<https://www.pulumi.com/docs/reference/pkg/nodejs/pulumi/aws/lambda/#CallbackFunction>). We recently pulled in a dependency (`parquetjs`) that has a compiled sub-dependency (`lzo`). We've now noticed that every time we rebuild our `node_modules` directory (with `npm ci`), the hash of the compiled `lzo` module changes, causing pulumi to want to redeploy all of our lambdas (even though no deps have actually changed).

Is there an elegant workaround to prevent pulumi from continuously redeploying our lambdas? We've already tried excluding `lzo` in `codePathOptions`.

cc <@UG77VR58X>

<@UB3BGTV63> do you have any insight on this by chance?

Submitted as bug at: <https://github.com/pulumi/pulumi/issues/4751>

Oops, sorry, <@UG77VR58X> not sure how I missed you tagging me here. I replied to the issue without any great ideas unfortunately