lambdaforge-local 0.1.1

Local AWS Lambda testing: generate realistic trigger events and invoke handlers with mocked AWS services

lambdaforge

Local AWS Lambda testing made simple.

Generate realistic trigger event payloads and invoke your Python Lambda handler locally — with optional in-memory AWS service mocking via moto. No Docker. No SAM. No LocalStack.

Install

pip install lambdaforge-local

Quick Start

# 1. Generate a realistic event file for your trigger type
lambdaforge generate --trigger apigateway

# 2. Edit event.json with your actual path, body, etc.

# 3. Invoke your handler
lambdaforge invoke --handler src/handler.py::lambda_handler

# With mocked DynamoDB and S3 (boto3 calls intercepted, no real AWS)
lambdaforge invoke --handler src/handler.py::lambda_handler --mock dynamodb,s3

Supported Triggers

Trigger	CLI value
API Gateway REST proxy	apigateway
SQS	sqs
S3 object created	s3
SNS	sns
EventBridge / scheduled	eventbridge

Supported Mock Services

Pass any combination via --mock: dynamodb, s3, ssm, sqs, sns

Note: Mocked services start empty. Pre-populate state in your handler behind an env var guard if needed. Seed file support is planned for v2.

How It Works

generate writes a complete AWS event JSON to a file (default: event.json). User-supplied fields are marked with "<placeholder>" strings.

invoke loads your handler via Python's import system, builds a mock LambdaContext, optionally activates moto's mock_aws() context, and calls handler(event, context). Output is formatted with rich.

License

MIT