Package Exports
- colly
This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (colly) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
Colly
Another serverless framework for AWS Lambda and API Gateway.
Instructions
Init a new Lambda
colly init-lambda --lambda_name <NAME_OF_LAMBDA>Run a lambda locally
colly run-lambda --name <NAME_OF_LAMBDA> --localYou can pass the Lambda an event object (use a JSON file in your project directory):
colly run-lambda --name <NAME_OF_LAMBDA> --local --event <RELATIVE_PATH_TO_JSON_FILE>Deploy a lambda
colly deploy-lambda --name <NAME_OF_LAMBDA> --aws_profile <AWS_PROFILE_NAME>Run a deployed lambda from the CLI
colly run-lambda --name <NAME_OF_LAMBDA>You can pass the deployed Lambda an event object (use a JSON file in your project directory):
colly run-lambda --name <NAME_OF_LAMBDA> --event <RELATIVE_PATH_TO_JSON_FILE>Developing
Configuration is done with environment variables. To run a node module directly (rather than via the commands in the bin) you need to set environment variables. Use this pattern:
env <VAR_NAME>="<VAR_VALUE>" node lib/<MODULE_NAME>For example...
env COLLY__PROJECT_DIR="./test/fixtures/deploy-lambda" ENV="live" node lib/deploy-lambda