Explain to me please what is the best way to locally test the lambda function. I used sam local and this solution https://github.com/lambci/docker-lambda
for testing, but for example, where I invoke one lambda from another error occurs. In general, I can't make stubs for methods since lambda runs in a container
相关问题
- How to generate 12 digit unique number in redshift
- Use awslogs with kubernetes 'natively'
- Assume/switch role in aws toolkit for eclipse 2.0
- 'no SavedModel bundles found!' on tensorfl
- Installing Python dependencies in AWS Codestar wit
相关文章
- Right way to deploy Rails + Puma + Postgres app to
- how many objects are returned by aws s3api list-ob
- Web Test recorder does not allow me to record a te
- AWS S3 in rails - how to set the s3_signature_vers
- Passthrough input to output in AWS Step Functions
- Factory_girl has_one relation with validates_prese
- I cannot locate production log files on Elastic Be
- What is the difference between `assert_frame_equal
This is how I test local lambda functions without Serverless frameworks, I run an HTTP post on local (quite easy setup for Go)
For local manual testing (not unit testing) with
sam cli
you can specify the environment varilables file with the-n, --env-vars PATH
option and use your real resource identifiers like you would normally do within your Cloud Formation template (refer to the official documentation for more informations).This should let you invoke other functions directly and use a real DynamoDB table and all other AWS Cloud resources.
Note: if you use VSCode you can try this helper extension.
There are a couple of options. Following two are some popular ones.