Once we can return a list of all Sprouts currently flashed to a Rhizome (Ohmbrewer/rhizome#63), we should write a job or two that reads that list and 1) reports if what's on the Rhizome matches what's in Ohmbrewer and 2) adds/removes Sprouts as necessary to get it to match the Ohmbrewer-side list.
This would be helpful for a few different use-cases:
1) Rather than requiring the user to add/remove all Sprouts, we could send a subset and speed up that process.
2) Rather than requiring the user to pre-flash the Sprout configuration, we could call this job(s) at the start of a batch run.
3) If there's a power outage, hard fault, or other Rhizome reboot during the batch run, we'd be able to recover by running this job. Currently, we have to do a full stop.
Once we can return a list of all Sprouts currently flashed to a Rhizome (Ohmbrewer/rhizome#63), we should write a job or two that reads that list and 1) reports if what's on the Rhizome matches what's in Ohmbrewer and 2) adds/removes Sprouts as necessary to get it to match the Ohmbrewer-side list.
This would be helpful for a few different use-cases: 1) Rather than requiring the user to add/remove all Sprouts, we could send a subset and speed up that process. 2) Rather than requiring the user to pre-flash the Sprout configuration, we could call this job(s) at the start of a batch run. 3) If there's a power outage, hard fault, or other Rhizome reboot during the batch run, we'd be able to recover by running this job. Currently, we have to do a full stop.