You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are two mutations which are relevent to jobs:
Poll
Kill
Currently, these are implemented as task mutations for historical reasons. This means that we cannot poll or kill an arbitrary job, only the latest instance via the task.
We should preserve the ability to run these mutations against tasks as it's useful to be able to poll/kill the latest submission without knowing its number, however, we should add job mutations for finer control.
This essentially boils down to addressing this TODO:
There are two mutations which are relevent to jobs:
Currently, these are implemented as task mutations for historical reasons. This means that we cannot poll or kill an arbitrary job, only the latest instance via the task.
We should preserve the ability to run these mutations against tasks as it's useful to be able to poll/kill the latest submission without knowing its number, however, we should add job mutations for finer control.
This essentially boils down to addressing this TODO:
cylc-flow/cylc/flow/network/schema.py
Lines 2187 to 2188 in 94fd7ac
And adding job filtering into the kill/poll commands.
The text was updated successfully, but these errors were encountered: