ghansham

I think we can use onSuccess, onFailure, onCancelled hooks to plugin the callbacks/scripts like messaging users via social apps, mail log files and what not.

One possible list of tasks could be we may have access to something like failed steps list, their stdout/stderr logs, return codes, etc easily accessible via variables and tasks defined...

Any update on this?

Will this create yaml and history?

This will be very useful feature. We should have a flag to ignore retry independent of pre condition. Ignore retry switch can be controlled from UI. We too have a...

We may need some parser in go that parse statements like: ($var1 == 1 || $var1 == 3) && $var2 == 4 and help in evaluating conditions. We can think...

Thanks for giving the details. May be in the elementary condition also we can support optional operators like eq, ne, in, notin (default case being eq) E.g. ```yaml - condition:...

Good idea. We can go ahead with this. Other than key=value also consider: ``` "key != value" "key in [list]" "key not in [list]" ```

May because we can add log level entry in base.yaml that controls the kind of log messages. Coming from java world, we used to have log level set to INFO,...

Just a quick solution, calling curl post request can do the trick. And the better part is it can work from remote system as well. Refer to: https://dagu.readthedocs.io/en/latest/rest.html#submit-dag-action-post-api-v1-dags-name For example...