[Feature Request] Add multiple schedules to a function

[kevin-lindsay-1]

My actions before raising this issue

• [x] Followed the troubleshooting guide
• [x] Read/searched the docs
• [x] Searched past issues

When using cron, if you need to schedule a job at, say, every 90 minutes, you actually need two cron schedules to accomplish that.

To accommodate that, I think it would be fairly easy to make the schedule annotation a comma-separated list.

Expected Behaviour

To schedule a function to run every 90 minutes: schedule: "0 0-21/3 * * *,30 1-22/3 * * *". AFAIK the timezone is always UTC.

Current Behaviour

I don't think the cron connector supports multiple schedules for a single function.

Possible Solution

Comma separated list of schedules.

Steps to Reproduce (for bugs)

Context

I have a job that needs to wait 90 minutes between attempts.

Your Environment

• FaaS-CLI version ( Full output from: faas-cli version ):

• Docker version docker version (e.g. Docker 17.0.05 ):

• Are you using Docker Swarm or Kubernetes (FaaS-netes)?

• Operating System and version (e.g. Linux, Windows, MacOS):

• Code example or link to GitHub repo or gist to reproduce problem:

• Other diagnostic information / logs from troubleshooting guide

Next steps

You may join Slack for community support.

[derek[bot]]

Please complete the whole issue template, without deleting any headings.

[kevin-lindsay-1]

this is not a bug. i'm not sure what derek's complaining about here, because I didn't edit the template.

i'm not going to fill in bug report information just to appease this bot, because this is not a bug report.

[kevin-lindsay-1]

I looked at the underlying cron library that this connector uses, and it looks like it supports @every <duration> schedules. Testing.

[kevin-lindsay-1]

It looks like the @every syntax works. I'll reopen if I have any more problems.

[alexellis]

So was no change required in this instance?

[alexellis]

I've turned off that Derek feature :upside_down_face:

[kevin-lindsay-1]

So was no change required in this instance?

it was not. the upstream cron scheduling package covers cases such as @every 1h30m. If you need precise scheduling of a function, such as every hour and a half at the 00 and 30 minute-marks, you'd need multiple schedules, though.

@every is based off when you started scheduling, so if you choose 1h30m, it will be 1h30m from when the schedule began. No way to choose specific times.