Details
-
Feature
-
Status: Released (View Workflow)
-
Minor
-
Resolution: Fixed
-
1.12.4, 1.13
-
None
Description
Current Situation
- When creating events the expiration date and time must be specified in the UTC time zone since
JITL-467. - When creating events with JOC Cockpit in the GUI the local time is used and is converted to UTC.
- When creating events with the JobSchedulerSubmitEventJob the UTC time zone must be used.
Desired Behavior
- It should be possible to specify the time zone for the given expiration date and cycle. The default for the time zone is UTC. A new parameter expires_timezone should be available to specify the time zone for the expiration date and cycle.
- The parameters scheduler_event_expires and scheduler_event_expiration_cycle in the job sos.scheduler.job.JobSchedulerSubmitEventJob will consider the parameter expires_timezone. The Parameter expires_timezone can be set for the JobSchedulerSubmitEventJob per event or centrally in the job sos.scheduler.job.JobSchedulerEventJob
- The API call events/custom/add_event will consider the parameter timezone in the post body for the expiration date.
- The PowerShell cmdlet Add-JobSchedulerEvent will consider the -Timezone parameter to convert the value of the -ExpirationCycle parameter.
- The allowed timezones are listed in the attached list of timezones
- The short ids will be mapped to one of the allowed timezones. Please refere for the mapping to this list https://docs.oracle.com/en/java/javase/12/docs/api/java.base/java/time/ZoneId.html#SHORT_IDS