Lesson 3: Types of Alarm Feed

In addition to the /whisk.system/alarms/interval feed in Lesson 2, the alarms provider in Adobe I/O Runtime supports other types of feeds.

Firing a trigger once

The /whisk.system/alarms/once feed allows you to fire an event once at a specific time. The only required parameter is date, indicating when to fire the trigger. Optional parameters are trigger_payload and deleteAfterFire.

triggers:
  runMeOnce:
    feed: /whisk.system/alarms/once
    inputs: 
      date: YYYY-MM-DDTHH:mm:ss.sssZ
      deleteAfterFire: true
Copied to your clipboard
triggers:
  runMeOnce:
    feed: /whisk.system/alarms/once
    inputs: 
      date: YYYY-MM-DDTHH:mm:ss.sssZ
      deleteAfterFire: true

Note that YYYY-MM-DDTHH:mm:ss.sssZ is just a format for this field; you are free to update it with the date and time you want.

Firing a trigger on a time-based schedule using cron

The /whisk.system/alarms/alarm feed allows you to fire an event on a time-based schedule using cron. This is more generic than the interval and once feeds, because you can write crontab to configure the alarm service to trigger at the exact time and interval you want. The only required parameter is cron, a string based on the UNIX crontab syntax that indicates when to fire the trigger in UTC. Optional params are trigger_payload, timezone, startDate and stopDate.

The following example shows a cron schedule at 2:00 am on Sundays in the Central Europe Timezone (CET):

triggers:
  sunday2am:
    feed: /whisk.system/alarms/alarm
    inputs: 
      cron: 0 2 * * 7
      timezone: CET
      startDate: 1601918992704
      stopDate: 1651918992704
Copied to your clipboard
triggers:
  sunday2am:
    feed: /whisk.system/alarms/alarm
    inputs: 
      cron: 0 2 * * 7
      timezone: CET
      startDate: 1601918992704
      stopDate: 1651918992704