swisscom/backman

cron schedules with comma

Closed this issue · 1 comments

JamesClonk commented

Currently any configured cron schedules in BACKMAN_BACKUP_SCHEDULES that contain a comma, for example "0 2,7,12,16,18,22 * * *" fail due to a parsing error.

  • Investigate env/config parsing library, can this behaviour by fixed without code changes?
  • Investigate using another configuration format and library for defining custom schedules
  • backman has to support cron schedules containing commas
JamesClonk commented

implemented new JSON configuration format in #3