Skip to content

Conversation

@floatingatoll
Copy link
Contributor

As noted in IAM-989, we aren't syncing timezones for a lot of workers due to their absence from tz_convert's manual table. IAM-992 removed the only instance of anyone parsing the timezone field, so this updates the HRIS publisher to just copy the Workday-provided timezone into the record without modification. This can be reversed later on if necessary.

Copy link

@gcoxmoz gcoxmoz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All users in the workday report have a Time_Zone (so we're into edge-cases) but, what if they don't.

If Time_Zone were ever missing, in the old world the .get would ship through tz_convert and be collapsed into string "UTC+0000 Europe/London". Now the timezone.value will be (I presume) pythonic None instead of a string.

You might want to make .get() have a UTC-ish default (nitpick, the old default of Europe/London isn't wholly UTC because of BST) or an empty string.

@floatingatoll
Copy link
Contributor Author

floatingatoll commented Nov 9, 2022

The CIS profile supports value null but I'm fine with empty string. Updated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants