feat: add timezone support to scheduling for Lambda functions #3016
Conversation
🦋 Changeset detectedLatest commit: c0e963a The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
| } else if ('cron' in schedule) { | ||
| return { ...schedule, timezone: schedule.timezone ?? DEFAULT_TIMEZONE }; | ||
| } | ||
| throw new Error("Could not determine the function's schedule type"); |
There was a problem hiding this comment.
This Error is not tested, can you include a test that covers it?
| }); | ||
| }); | ||
|
|
||
| void it('sets valid schedule - rate with timezone', () => { |
There was a problem hiding this comment.
Could you add some test cases for invalid inputs for rate and timezone (invalid timezone)?
|
One of our workflows is failing because the changeset bumps |
| @@ -0,0 +1,5 @@ | |||
| --- | |||
| '@aws-amplify/backend-function': minor | |||
There was a problem hiding this comment.
Need to bump @aws-amplify/backend too.
Problem
Function schedules are powered by Amazon EventBridge rules, so not supported timezone.
Migrate EventBridge Scheduler to support timezone.
Issue number, if available:
fix #3008
Changes
Added a function schedule format that specifies the timezone.
We migrated from EventBridge rules to EventBridge Scheduler to support time zones.
Corresponding docs PR, if applicable:
aws-amplify/docs#8448
Validation
Checklist
run-e2elabel set.By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.