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

image.png

Is that an error when you invoke the lambda or when you run `pulumi up`? (Looks like cloudwatch but wanted to confirm)

the error comes after running Pulumi Up and after invoking the lambda

In that case, it looks like you’re missing a package that your lambda code is expecting. 

Not really no. I’ve been using these Lambda functions for a year with no change. And today I did a deployment and got this issue. 

The error goes away when using CodeBuild. Same commands are executed in codebuild.

Not sure why it only happens in local env and for
About 50 of my lambdas 

Is this the first time you’ve used Pulumi to deploy these lambda functions? Can you share the Pulumi code you’re using?

No, I’ve been using pulumi for the past 2 years 

I don’t think I could share the code as it would violate my companies nda. Is there any other way we could work this out ?

What changes were made between the last deployment and this one?

So no changes to the lambda code and no changes to the Pulumi code. How are you running `pulumi up`? You mentioned that it ran on code build. How are you running it otherwise?

For local development I run it on my pc.
But for dev env releases we use codebuild and that issue fixes

I created a build for the same stack and when running the same stack creating the error through codebuild, it disappears ! 

My guess is in local deployment some modules don’t get bundled!