With cron, broadcast and device request handling factored out (into oceancron, oceantv and datablue respectively), it no longer makes sense for Ocean Bench to be an endpoint for site health checking.
Given the temporal nature of site health checking, it is proposed to deprecate the use of cron.yaml and move this functionality to oceancron. A new built-in cron check action would either check a site as a whole (i.e., all of its devices) or check a single device for the given site.
Site administrators wishing to routinely check the health of their site and/or devices need only create cron jobs that call this function at the desired frequency.
scruzin
commented
4 weeks ago
With cron, broadcast and device request handling factored out (into oceancron, oceantv and datablue respectively), it no longer makes sense for Ocean Bench to be an endpoint for site health checking.
Given the temporal nature of site health checking, it is proposed to deprecate the use of cron.yaml and move this functionality to oceancron. A new built-in cron check action would either check a site as a whole (i.e., all of its devices) or check a single device for the given site.
Site administrators wishing to routinely check the health of their site and/or devices need only create cron jobs that call this function at the desired frequency.