I can milk the cows (or update health) on demand for just a single commons.
So that I have more control over individual games
Discussion
Currently on the Admin/Jobs page the admin can choose a specific commons when:
setting cow health to a specific value
requesting an instructor report
However, the jobs to milk the cows and update cow health (note: different from "setting" cow health) can only be run for all commons, or none at all.
It would be nice, building on the functionality for "set cow health" and "instructor job (specfic commons) to be able to specify a commons, or "all", when running the "update cow health" and "milk the cows" jobs.
However, this has to be done carefully, since the automated job that updates cow health and milk cows on a schedule needs to still work on all commons; so it's not ok to make the commonsId parameter required, and take away the ability to update health for all commons, or milk all cows. That needs to be retained.
Acceptance Criteria
(Note this issue could be broken into multiple issues/PRs)
[ ] Either: the backend endpoint that launches the job to milk the cows can take an optional parameter specifying a particular commonsId (if not specified, then the job is run for all commons). OR there is a separate endpoint for milking cows for a particular commons.
[ ] Either: the backend endpoint that launches the job to update cow health can take an optional parameter specifying a particular commonsId (if not specified, then the job is run for all commons). OR there is a separate endpoint for updating cow health for a particular commons.
[ ] There is a way on the jobs page to specify a commons when submitting the milk the cows job. This can be a selector similar to the one on the page for setting the health of all cows for a particular commons, except that in addition to an option for each commons, at the top there is an option "ALL" which specifies that the cows should be milked for all commons. OR there are separate section on the jobs page for Milking Cows (specific commons) and milking cows (all commons). This is an implementer choice.
[ ] There is a way on the jobs page to specify a commons when submitting the update cow health job. This can be a selector similar to the one on the page for setting the health of all cows for a particular commons, except that in addition to an option for each commons, at the top there is an option "ALL" which specifies that the cows should be milked for all commons. OR there are separate section on the jobs page for Update Cow Health (specific commons) and Update Cow Health (all commons). This is an implementer choice.
User Story
Discussion
Currently on the Admin/Jobs page the admin can choose a specific commons when:
However, the jobs to milk the cows and update cow health (note: different from "setting" cow health) can only be run for all commons, or none at all.
It would be nice, building on the functionality for "set cow health" and "instructor job (specfic commons) to be able to specify a commons, or "all", when running the "update cow health" and "milk the cows" jobs.
However, this has to be done carefully, since the automated job that updates cow health and milk cows on a schedule needs to still work on all commons; so it's not ok to make the commonsId parameter required, and take away the ability to update health for all commons, or milk all cows. That needs to be retained.
Acceptance Criteria
(Note this issue could be broken into multiple issues/PRs)