Now that I realized that the lambda_function.lambda_handler naming
isn't hard-coded in AWS but is instead just a default, (and now that
I've configured it to this instead).
deploy-lambda:
rm -rf .deploy-lambda-source
git clone . .deploy-lambda-source
- (cd .deploy-lambda-source/turbot_lambda; zip ../turbot.zip lambda_function.py)
+ (cd .deploy-lambda-source/turbot_lambda; zip ../turbot.zip turbot_lambda.py)
(cd .deploy-lambda-source; zip turbot.zip $$(git ls-files -- turbot))
(cd .deploy-lambda-source; \
aws lambda update-function-code \
+++ /dev/null
-from turbot.rot import rot
-
-def lambda_handler(event, context):
- """Top-level entry point for our lambda function.
-
- Currently only calls into the rot() function but may become more
- sophisticated later on."""
-
- result = rot(event['args'])
-
- return {
- 'statusCode': 200,
- 'body': result
- }
--- /dev/null
+from turbot.rot import rot
+
+def turbot_lambda(event, context):
+ """Top-level entry point for our lambda function.
+
+ Currently only calls into the rot() function but may become more
+ sophisticated later on."""
+
+ result = rot(event['args'])
+
+ return {
+ 'statusCode': 200,
+ 'body': result
+ }