Closes #88
The date/time parsing in AutosysSensor is format sensitive. We can use dateutil.parser to make the process format agnostic.
Description
Using the dateutil.parser to make internal logic of AutosysSensor agnostic to the format of the execution_date provided by the Brickflow context; and using the same approach to parse lastEndUTC string to timestamp.
This solves the cases when/if upstream Autosys API changes and the lastEndUTC timestamp is provided in different format;
It solved error when parsing the execution_date which format may be different depending on how the job is triggered.
How Has This Been Tested?
Screenshots (if appropriate):
Types of changes
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
Checklist:
[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
Closes #88 The date/time parsing in AutosysSensor is format sensitive. We can use
dateutil.parserto make the process format agnostic.Description
Using the
dateutil.parserto make internal logic of AutosysSensor agnostic to the format of theexecution_dateprovided by the Brickflow context; and using the same approach to parselastEndUTCstring to timestamp.Related Issue
[BUG] Faulty execution_date parser in AutosysSensor
Motivation and Context
This solves the cases when/if upstream Autosys API changes and the
lastEndUTCtimestamp is provided in different format; It solved error when parsing theexecution_datewhich format may be different depending on how the job is triggered.How Has This Been Tested?
Screenshots (if appropriate):
Types of changes
Checklist: