Ryan Petrello 15906b7e3c
support TZID= in schedule rrules
this commit allows schedule `rrule` strings to include local timezone
information via TZID=NNNNN; occurrences are _generated_ in the local
time specific by the user (or UTC, if e.g., DTSTART:YYYYMMDDTHHMMSSZ)
while Schedule.next_run, Schedule.dtstart, and Schedule.dtend will be
stored in the UTC equivalent (i.e., the scheduler will still do math on
"what to run next" based on UTC datetimes).

in addition to this change, there is now a new API endpoint,
`/api/v2/schedules/preview/`, which takes an rrule and shows the next
10 occurrences in local and UTC time.

see: https://github.com/ansible/ansible-tower/issues/823
related: https://github.com/dateutil/dateutil/issues/614
2018-01-22 11:50:00 -05:00
..
2018-01-10 09:26:11 -05:00
2017-04-12 16:19:42 -04:00
2017-07-14 13:58:08 -04:00
2017-06-12 12:01:30 -04:00
2017-11-16 12:48:48 -05:00
2017-06-16 09:40:27 -04:00
2016-05-13 12:01:54 -04:00
2018-01-22 11:50:00 -05:00