Unable to deploy single lambda function for version 1.52.1
See original GitHub issuesls deploy -f “function_name” is not working throwing and exception
My serverless version is:
Framework Core: 1.52.1
Plugin: 3.0.0
SDK: 2.1.1
sls deploy -f function_name
is not working
it throws and errors the complete trackback would be
TypeError: Cannot read property 'artifact' of undefined at ServerlessPythonRequirements.BbPromise.bind.then.then.then (/home/mahesh/shuttle/H2OLambda/pythonh20lambda/node_modules/serverless-python-requirements/index.js:176:48)
Any update on this would be appreciated. Thank you
Issue Analytics
- State:
- Created 4 years ago
- Reactions:41
- Comments:46 (7 by maintainers)
Top Results From Across the Web
Troubleshoot deployment issues in Lambda
Error: Unable to load type 'Function.Handler' from assembly 'Function'. The name of the file or class in your function's handler configuration doesn't match ......
Read more >Using Lambda Versions, Aliases and Safe Deployments with ...
In this article I discuss the merits of using Lambda versioning and aliases along with the AWS Serverless Application Model's (SAM) built-in ...
Read more >Deploy Function - AWS Lambda - Serverless Framework
The sls deploy function command deploys an individual function without AWS CloudFormation. This command simply swaps out the zip file that your ...
Read more >How to upgrade CDK from CDKv1 to CDKv2 in an existing ...
On december 2nd AWS announced the general availability of CDK version 2. The main reason that the CDK team released version two was...
Read more >terraform-aws-modules/lambda/aws
Create, update, and publish AWS Lambda Function and Lambda Layer ... to either one version of Lambda Function (when deployment complete), ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@ovunccetin Your workaround can be shorten to just:
I found a workaround but I’m not sure about the side effects.
The problem is the following line (line # 176 in my version) in serverless-python-requirements/index.js file:
It simply assumes the existence of package.artifact path in your function definition in serverless.yml.
As a work around I added "package: artifact: " to my function as follows and it worked:
Again, I’m not sure if this breaks anything else. I have just tried an individual function deployment and it worked. But I didn’t make a detailed test.