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 @worried-engineer-33884

@white-balloon-205 do you have any insight on this by chance?

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

Oops, sorry, @worried-engineer-33884 not sure how I missed you tagging me here. I replied to the issue without any great ideas unfortunately