jetclosing / serverless-plugin-ignitor Goto Github PK

See instructions:

https://github.com/serverless/plugins#community-contributed-plugins

• Add default config options for "invoke on deploy" and ignitor rate
• Schedule option should be made more flexible to allow custom schedules + rates
• Per function overrides for invoke on deploy and ignitor rate
• Terminal/Console warning when no matches
• unit tests for index.js
• add serverless-plugin keyword to package.json
• add eslint
• Specify aws provider: https://serverless.com/framework/docs/providers/aws/guide/plugins#provider-specific-plugins
• add npm badges to README:

![npm downloads total](https://img.shields.io/npm/dt/serverless-plugin-ignitor.svg) ![npm version](https://img.shields.io/npm/v/serverless-plugin-ignitor.svg) ![npm license](https://img.shields.io/npm/l/serverless-plugin-ignitor.svg)

It appears there is a hard default cap of 100 rules per region. https://docs.aws.amazon.com/AmazonCloudWatch/latest/events/cloudwatch_limits_cwe.html

To avoid this we might restructure how rules + lambdas are called, and allow that subset of lambdas to delegate events asynchronously to child lambdas.

Dynamic Lambdas, rules, and events can be leveraged to perform this. However we might want to see how the interference of a delegate lambda, and a custom defined lambda operates before moving futher.