We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I packaged my own artifacts with the same zip file name:
/packages/foo/bin/lambda.zip /packages/bar/bin/lambda.zip /packages/boo/bin/lambda.zip
When I deployed my functions they all had the same code.
Serverless should have renamed the artifacts based on the function name when uploading to S3 so that they didn't overwrite each other.
/packages/foo/bin/lambda.zip -> s3://deploy/serverless/service/stage/timestamp/foo.zip /packages/bar/bin/lambda.zip -> s3://deploy/serverless/service/stage/timestamp/bar.zip /packages/boo/bin/lambda.zip -> s3://deploy/serverless/service/stage/timestamp/boo.zip
template: handler: index.handler package: artifact: packages/template/bin/lambda.zip web: handler: index.handler package: artifact: packages/web/bin/lambda.zip
No errors, my functions were just all the same.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
This is a Bug Report
Description
I packaged my own artifacts with the same zip file name:
When I deployed my functions they all had the same code.
Serverless should have renamed the artifacts based on the function name when uploading to S3 so that they didn't overwrite each other.
No errors, my functions were just all the same.
Additional Data
The text was updated successfully, but these errors were encountered: