CLI

These commands and the project should be created in your project's code repository so you can use your CI/CD toools (travis, circleci, bitbucket pipelines, etc.) to kick off the test when new code is introduced. The CLI assumes you have credentials stored at ~/.aws/credentials or wherever your OS stores them. If you want to use a profile other than the default profile use the --profile_name argument.

Essential Commands

Create a New Project

This command creates will ask you a few questions and then create a file named loadlamb.yaml that stores those answers along with a sample request.

loadlamb create_project

Create a New Extension

This command creates a new extension. This is useful for creating new request types and tasks that need more than one request.

loadlamb create_extension

Deploy LoadLamb

This command zips the requirement libraries, the core loadlamb code, custom extension, and uses a SAM template to deploy the Lambda functions (push_handler and pull_handler), DynamoDB table, SQS message, and a new role via CloudFormation.

loadlamb deploy

Run LoadLamb

This command uses boto3 to execute the push_handler Lambda function by using the contents of the loadlamb.yaml as the event (payload) argument. Which sends the config as an SQS message.

loadlamb execute --stage dev --region us-east-1 --filename loadlamb.example.yaml --profile_name default

Non-Essential Commands

Create the SAM Template

This command creates a SAM template named sam.yml.

loadlamb create_template

Create the Code's Zip File

This command zips the requirement libraries, the core loadlamb code, and custom extensions up in a zip file.

loadlamb create_package