- Record step function ARN in deployed values. Fixes #22
- Return enclosed function in ALB decorator
- Minor documentation improvements
- Manage route53 records for ALB
- Initial support for ALB
- Condense SNS/SQS names for brevity
- Add app.state_machine.start_named_execution(name, *args)
Retain S3-SQS mux ability
Build SNS-SQS bridge to mux lambdas onto S3 event types
Fix essential logging, take 4
Fix essential logging, take 3
Fix essential logging, take 2
Fix essential logging
- Enable refresh deployment in packager
- Use Python logging library instead of Lambda context.log (#11, thanks to @irgeek)
- Remove debug statement
- Grant SQS permissions to invoke lambda
- Allow queue attributes to be set in SQS
- SQS S3 event envelope support
- Support state machine introspection and SQS-SFN springboard
- Update docs for SQS
- Don’t assume eventSource exists
- Add support for SQS event sources
- Set function description from “description” config key
- Fix version reporting and provide it in published Lambda tag
- Domovoi is now compatible with Chalice 1.2+. This should be a backwards compatible change. However, Chalice underwent a complete deployment system rewrite in version 1.2, so deployment state or other aspects of your app’s deployment may be affected. You may need to clear the deployment state of your app.
- Allow customizable rule name for @scheduled_function (fixes #9)
- Ensure domovoi errors when there is no handler
- Allow configurable concurrency reservation
- Add support for new-project and update docs
- Skip updating event source mapping when diff is null
- Avoid triggering Lambda API rate limits when managing state aliases
- Ensure SNS topic names can represent all DNS-compliant S3 bucket names. Fixes #5
- Fix routing of domovoi dynamodb handlers
- Add DynamoDB streams support
- Bypass prompt when writing IAM policy for the first time
- Only call step_function_task if the state has a Resource field that's callable
- Allow state machine registration; pass state name in context
- Deconflict concurrent S3 notification config operations
- Improve SM updates: use update_state_machine
Accommodate eventual consistency in SM update loop
- Add statement to debug SM deploy loop crash
- Add support for CloudWatch Logs subscription filter events
- Expand docs for step function / state machine examples
- Support nested states
- Key state machine tasks by state name, not function name
- Parameterize sfn trust statement by region
- Add step functions support
- Monkey-patch chalice to avoid dependency wheel management bug
- Use more intuitive errors when handler not found
Avoid running privileged op on update
- Chalice 1.0 compat, part 3
- Chalice 1.0 compat, part 2
Chalice 1.0 compatibility fixes
- Simplify DLQ handling; add docs for DLQ
- Support DLQ lambda config
- Parameterize stage name, part 2
- Parameterize stage name
- Forward S3 notifications through SNS by default
- Don't clobber existing S3 bucket notifications
- Pass through configure_logs
- Test improvements
Fix error in release
Enable idempotent Lambda permission grants
- Hardcode no autogen policy
- Ensure S3 bucket notifications work without filters specified
- Fix dispatching of S3 events
- Fixes to deploy procedure
- Fix event subscriptions
- Update to be compatible with Chalice 0.8 and Python 3.6
- Autogenerate IAM policy
- Release automation
- Initial release.