feat: allow scheduled function to specify timezone #173
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Thank you for helping out! ✨
We really appreciate your commitment to improving Architect
To maintain a high standard of quality in our releases, before merging every pull request we ask that you've completed the following:
mainnpm itfrom the repo root)readme.md, help docs, inline docs & comments, etc.)changelog.mdThis PR adds support for the timezone property. Instead of using
AWS::Events::Ruleit updates scheduled functions to useAWS::Scheduler::Schedulewhich supports setting a timezone.All existing tests pass and added new test coverage.
Did manual testing by deploying a scheduled function with the following arc:
and was able to verify in CloudWatch logs that it did run at 4:30pm in the Eastern timezone.