digdag
digdag copied to clipboard
Workload Automation System
## Summary A task logs can't display correctly until reload browser.  Reported-by: [showyu](https://twitter.com/showyou/status/1140778569871896576) ## Reproduce steps ``` mkdir /tmp/log digdag server -m -O /tmp/log ``` ``` digdag init -t...
Hi all, I have a feature request. I want `_canceled` parameter for some cleanup tasks. When a workflow is canceled, we cannot hook any tasks currently. Sometimes I define a...
Some system configuration parameters are missing document. * `http>` operator * config.http.allow_user_proxy * config.http.max_redirects * config.http.max_stored_response_content_size * config.http.proxy.enabled * config.http.proxy.host * config.http.proxy.port * config.http.proxy.tls * config.http.user_agent * `mail>` operator [Release...
Hi there. It would be great if digdag have a pop-up window when pressing the button to stop or resume the workflow schedule. In addition, it is also useful when...
## Overview notification.shell.command log is throw away to `dev/null` in the following code. https://github.com/treasure-data/digdag/blob/master/digdag-core/src/main/java/io/digdag/core/notification/ShellNotificationSender.java#L56 So. It makes difficult to debug notification scripts. ## Reproduction digdag.conf ``` notification.type = shell notification.shell.command...
## Overview if error in `_export` then `_error` task is not execute. ## Reproduction Reference to `huga` in `_export`, but `huga` is not difined. And, I expect run `echo error!!!!!!!!!`...
``` _export: orig: key: 1 +task1: _export: alias: ${orig} sh>: echo ${alias} # {key:1} +task2: _export: alias: ${orig} sh>: echo ${alias.key} # empty ``` I expected that `${orig}` gives me...
PgJDBC 42.2.0 has been released. It support get/setNetworkTimeout() in connections feature. This feature will fix #583. https://github.com/pgjdbc/pgjdbc/blob/master/CHANGELOG.md#added
Some environments don't allow direct any outbound connections. Digdag client users in such environments need to use HTTP proxy to connect to digdag server. Idea here is to add support...
This can be useful for the workflow where it's important to ensure the presence of table(s) at all times