MetRonnie
commented
3 years ago Having a separate command might be tricky, due to the two types of task matching (dumping explanation here as it may be useful to whoever tackles this):
which matches spawned tasks (hidden + main pool). It looks like this is used by cylc kill for example.
And
which matches any task that is in the graph, whether it has spawned or not. I think this is use by cylc trigger.
Additionally, cylc hold uses both
Some Cylc subcommands allow us to glob over the active task window e.g.
cylc trigger.It would be useful if there was a way to get a list of the tasks that this would trigger before triggering.
Ideas:
--dryoption (prints list of tasks).-i, --interactiveoption (prints list of tasks with a y/n prompt).We can also print out the list of the tasks that were triggered, note this aspect is currently blocked by #3329 due to the command queueing system.
Additional context
Pull requests welcome!