KeonHee opened a new issue #207: strict option does not work URL: https://github.com/apache/openwhisk-package-alarms/issues/207 I created alarm trigger with `strict=true` ``` wsk trigger create periodic28 \ --feed /whisk.system/alarms/alarm \ --param cron "*/1 * * * *" \ --param trigger_payload "{\"name\":\"Odin\",\"place\":\"Asgard\"}" \ -p strict true ok: invoked /whisk.system/alarms/alarm with id deb8f8316cbd4be9b8f8316cbd7be9eb ok: created trigger periodic28 ``` If the `strict = true` is given, the cron job should run in 0 seconds, which is actually created with a value of `13 * / 1 * * * *`. ``` [2020-03-06T04:09:25.695Z] [INFO] [worker1] [lambda-alarm-worker1-test-76cc465994-xsh7j] [alarmsTrigger] [setupFollow] got change for trigger xxxxxxxx/geonhui/periodic28 [2020-03-06T04:09:25.696Z] [INFO] [worker1] [lambda-alarm-worker1-test-76cc465994-xsh7j] [alarmsTrigger] [distributeCronAlarm] xxxxxxxx/geonhui/periodic28 is converted to "13 */1 * * * *" [2020-03-06T04:09:25.696Z] [INFO] [worker1] [lambda-alarm-worker1-test-76cc465994-xsh7j] [alarmsTrigger] [scheduleCronAlarm] xxxxxxxx/geonhui/periodic28 starting cron job [2020-03-06T04:09:25.697Z] [INFO] [worker1] [lambda-alarm-worker1-test-76cc465994-xsh7j] [alarmsTrigger] [setupFollow] xxxxxxxx/geonhui/periodic28 created successfully ```
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
