-
Notifications
You must be signed in to change notification settings - Fork 214
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
EventBridge Scheduler Integration for Stepfunction #571
Comments
Please follow the work for the same in the following repository: |
Is there any update on adding this feature? |
This is an essential enhancement to this plugin to maintain parity with Serverless. See serverless/serverless#11935 @jappurohit041 @KillDozerX2 Can you make your PR to this repository so it can have a chance of getting merged and released? |
Yeah, getting there. |
Apologies for the delay, we've opened a new PR for this. #580 |
🎉 This issue has been resolved in version 3.15.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Hi @KillDozerX2, @jappurohit041, @horike37 It seems like there is a key piece that was missed here. There is no way to pass input into the target. There are no errors when an input is passed, but when deployed, it never gets set. Serverless allows for this functionality with Lambdas (see here) Cloudformation also allows for this pretty simply (see here) I imagine this was just missed or overlooked when adding this new code (see here) because errors were added for InputPath and InputTransformer. Can this issue be re-opened for this functionality to be added? |
🎉 This issue has been resolved in version 3.17.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Feature Proposal
For feature proposals:
-> Ability to create AWS::Scheduler::Schedule triggers as an alternative to AWS::Event::Rule, which may be preferable if hitting account-wide limits on a number of AWS::Event::Rule triggers per bus (Lambdas are only able to be triggered from the default bus).
-> Also, specify a timezone to run it on local time.
The text was updated successfully, but these errors were encountered: