Let's say there is an update that needs to be applied, especially in Docker, which may include an array of services in a single stack. Currently the options are to kill/fail the current tasks, which will likely start new tasks anyway, or pause them, which may cause them to fail after a reload.
It would be nice to have an option to stop processing tasks after the current ones are complete so that updates can be applied cleanly without causing tasks to fail and having to clear them from the processed list.
I'm hoping this wouldn't be too much hassle and would save folks a lot of time and frustration.
Loving this so far, by the way. Very happy I found this. It's far easier to work with than the 'arr that must not be named.
Just a simple QoL improvement.
Let's say there is an update that needs to be applied, especially in Docker, which may include an array of services in a single stack. Currently the options are to kill/fail the current tasks, which will likely start new tasks anyway, or pause them, which may cause them to fail after a reload.
It would be nice to have an option to stop processing tasks after the current ones are complete so that updates can be applied cleanly without causing tasks to fail and having to clear them from the processed list.
I'm hoping this wouldn't be too much hassle and would save folks a lot of time and frustration.
Loving this so far, by the way. Very happy I found this. It's far easier to work with than the 'arr that must not be named.