At the moment, only one status filter can be given to the dagu history CLI command:
dagu history --status running
This can become a challenge when looking for runs across multiple possible statuses.
At the moment, the only way to do this is to either get all runs and filter them afterwards, or run the command multiple times.
I propose that the command also allows a comma-separated list:
dagu history --status running,queued
This would make it much easier to look for runs, especially in situations where a run has a very short lifespan and changes state quickly.
Thank you for your consideration.
At the moment, only one status filter can be given to the
dagu historyCLI command:dagu history --status runningThis can become a challenge when looking for runs across multiple possible statuses.
At the moment, the only way to do this is to either get all runs and filter them afterwards, or run the command multiple times.
I propose that the command also allows a comma-separated list:
dagu history --status running,queuedThis would make it much easier to look for runs, especially in situations where a run has a very short lifespan and changes state quickly.
Thank you for your consideration.