https://pulumi.com
Join Slack
This message was deleted.
# aws
s
This message was deleted.
f
Ciao fratello!
👋 1
I think the in-line lambda code is serialized and packaged in a way that just because the import/require is in the pulumi code file doesn’t mean it (or the required node_modules) make it into the zip file that is sent to AWS Lambda and executed at runtime
try the hacky 
NODE_PATH=$PWD pulumi up
to see if that helps drag the right dependencies along. If that works let me know and I have a smoother mechanism to try.
(See my recent pinned note in the #CJ909TL6P channel - because it’s even more dastardly when ts-node is in the mix)
c
Likely the import is in the Pulumi program, not the lambda When I was still using inline callbacks I would use 
require()
inside the callback for any imports
d
doesn't work with NODE_PATH and doesn't work with require. I think there's something else going on
possibly fixed with this, so I was right about the nohoist, but simply changing that it didn't work. I should have done a cleanup of all node_modules. Luckily I checked for an updated version of code-pipe and the node_modules got sorted out
👍 1
@fierce-camera-61577 I am still waiting on that blog post on localstack 😉 😄
f
I’m waiting for a 1 line deletion PR to be merged on LocalStack🙂
👀 1
d
@fierce-camera-61577 you managed to misspell both my name and family name 😂 but thanks for the mention
Toni Terreno 😉
f
I did it to make sure you read the article 😛
d
lol
6 Views
Open in Slack
PreviousNext
Powered by

Pulumi Community

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.

Powered by