-
Notifications
You must be signed in to change notification settings - Fork 5.7k
Add ability to create AWS::Scheduler::Schedule triggers and specify timezone #11935
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
Conversation
Also added timezone enum
…lues This will add better validation for users
renamed variable to being just `timezone`
@medikoo I took the existing PRs and fixed the merged conflicts and filled in any missing holes. I have also tested it and it seems to be working OK. Can you please give it a review when you get a chance? @joelwalden and @KillDozerX2 this PR includes the work you have done. So feel free to review this as well. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@tie624 great thanks for thaking that over, and sorry for late review.
It looks as great direction, please see my comments
lib/plugins/aws/package/lib/iam-role-lambda-execution-template.json
Outdated
Show resolved
Hide resolved
lib/plugins/aws/package/lib/iam-role-lambda-execution-template.json
Outdated
Show resolved
Hide resolved
test/unit/lib/plugins/aws/package/compile/events/schedule.test.js
Outdated
Show resolved
Hide resolved
test/unit/lib/plugins/aws/package/lib/merge-iam-templates.test.js
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you @tie624 that looks really good!
I have just a few I believe final suggestions, and we should be good to go 🎉
I also made the permissions more granular rather than using a wildcard to allow all functions. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for update @tie624. I have just a few last style suggestions
@medikoo changes made |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you @tie624 and sorry, there are still few thing which we should improve before merging this in
test/unit/lib/plugins/aws/package/compile/events/schedule.test.js
Outdated
Show resolved
Hide resolved
@medikoo please take another look. |
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## main #11935 +/- ##
==========================================
+ Coverage 86.68% 86.71% +0.02%
==========================================
Files 316 316
Lines 13439 13474 +35
==========================================
+ Hits 11650 11684 +34
- Misses 1789 1790 +1
☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great work @tie624 ! 🎉
Adds the ability to create AWS::Scheduler::Schedule triggers as an alternative to AWS::Event::Rule, which may be preferable if hitting account-wide limits on number of AWS::Event::Rule triggers per bus (Lambdas are only able to be triggered from the default bus).
Also allows you to specify a timezone to run it on local time.
Unless they need to use inputPath or inputTransformer, developers should be able to just add the method config option and seamlessly migrate to use Scheduler if the devs find themselves up against the account quotas.
Closes: #11680
Replaces: #11707
continues from the work of @joelwalden and @KillDozerX2