-
Notifications
You must be signed in to change notification settings - Fork 242
fix(hubs): make ADF trigger startTime Z-suffix conditional on UTC fallback #2291
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
base: dev
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -112,7 +112,11 @@ resource dataFactory 'Microsoft.DataFactory/factories@2018-06-01' existing = { | |
| recurrence: { | ||
| frequency: 'Hour' | ||
| interval: 24 | ||
| startTime: '2023-01-01T01:01:00' | ||
| // Data Factory requires a trailing 'Z' on startTime when timeZone resolves to 'UTC' (the | ||
| // fallback for regions not in timeZones.bicep's map); a missing 'Z' fails trigger activation | ||
| // with InvalidWorkflowTriggerRecurrence. Mapped, non-UTC regions must keep the no-'Z' format | ||
| // so they continue scheduling on local wall-clock time. | ||
| startTime: timeZones.outputs.Timezone == 'UTC' ? '2023-01-01T01:01:00Z' : '2023-01-01T01:01:00' | ||
|
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The conditional and the comment are both right, and I like that the second occurrence points back here rather than repeating the rationale. Non-blocking suggestion: pin this in Without it, the invariant lives only in a comment, and
Collaborator
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. nit: Should we update these to 2026? Not sure if there's an issue with a 3-year-old start date. Just a thought. Applies to the other 2 instances as well. |
||
| timeZone: timeZones.outputs.Timezone | ||
| } | ||
| } | ||
|
|
@@ -138,7 +142,8 @@ resource dataFactory 'Microsoft.DataFactory/factories@2018-06-01' existing = { | |
| recurrence: { | ||
| frequency: 'Month' | ||
| interval: 1 | ||
| startTime: '2023-01-05T01:11:00' | ||
| // See trigger_DailySchedule above for why the 'Z' suffix is conditional on the UTC fallback. | ||
| startTime: timeZones.outputs.Timezone == 'UTC' ? '2023-01-05T01:11:00Z' : '2023-01-05T01:11:00' | ||
| timeZone: timeZones.outputs.Timezone | ||
| schedule: { | ||
| monthDays: [ | ||
|
|
||
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.
Holding for validation