-
Notifications
You must be signed in to change notification settings - Fork 286
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dependencies are not packaged for the lambda which has Individual packaging (per lambda, not the top level). #744
Comments
Hey @amediantsev, thanks for reporting and sorry you've run into trouble there. It looks like you're using an outdated version of the Framework and not up-to-date version of the plugin. Could you please upgrade to latest versions if possible first? It might be that the issue is already resolved in older versions of the plugin |
@pgrzesik Thanks for responding. You are correct. Current versions: Framework Core: 3.25.0 (local) 3.25.0 (global) {... |
@amediantsev I am not sure if you still have this issue.
Line specifying the cache dir starts with Hope that helps |
@amediantsev did you get to solve this thing? |
I have the same issue trying to deploy inside a Bitbucket pipeline. Also, I'm using serverless compose to deploy two services:
The packaging for the second fails for 1 single lambda but randomly: sometimes it works, sometimes don't. I'm using the most recent versions and nodejs 20. |
Hey @jacksoncassimiro 👋 Sorry you've ran into trouble. I've tried to reproduce this bug but I was not successful in my attempts. Would you have the ability to share a reproducible example by any chance? Does it only fail when working Compose? If anyone else could provide a concrete repro example, I would be grateful 🙇 |
Are you certain it's a bug?
Are you using the latest plugin release?
Is there an existing issue for this?
Issue description
When individual packaging is defined per lambda, dependencies are not packaged for that lambda.
I.e.
We have a such function in serverless.yml:
and such project structure:
And libraries listed in
requirements.txt
are not packaged to the final MyIndividualFunction.zipService configuration (serverless.yml) content
N/A
Command name and used flags
N/A
Command output
Environment information
The text was updated successfully, but these errors were encountered: