digdag icon indicating copy to clipboard operation
digdag copied to clipboard

Workload Automation System

Results 100 digdag issues
Sort by recently updated
recently updated
newest added

Support for podman will be great. Podman has compatibility with Docker and works with docker images too. So I am guessing implementation in digdag should be straight forward. > What...

I'm happy if `interval` in `_retry` supports syntax like `3h`, `30m` and so on. ```yaml +task: _retry: limit: 3 interval: 1h #

Store params can't be referenced when retry failed to use call operator in the case of cousin relationship. ## example https://github.com/katsuyan/digdag-example/tree/master/store_retry ## Execution result Store params can be referenced when...

See also https://github.com/treasure-data/digdag/pull/1641#issuecomment-932850649 for details.

MomentJS is used in Digdag project tightly when we organize timestamp data. But, Unfortunately, Moment.js announced that they are going to be a legacy project in maintenance mode. We need...

enhancement
feature_request

EcsCommandExecutor supports two ways to get task definition. One is from TaskDefinitionArn and Others is from tag. Firstly it tries to find a task definition from the arn and if...

enhancement

## objective KubernetesCommandExecutor now throws an exception when the execution time of a pod exceeds the defaultPodTTL. But we also need to consider that the pod execution time may exceed...

enhancement

There is the strange behavior about workflow fire. I confirmed the behavior by the following step. 1. create a new workflow and schedule it (ex. every 5 min). ``` $...

bug

Now I consider the following DAG. (2, 3) and (4, 5) are executed in parallel, respectively. ![image](https://user-images.githubusercontent.com/35782950/144555193-d83f96e3-974b-47ac-959c-83e468d3414e.png) As far as I thought, this DAG cannot be represented in a format...

follow-up for https://github.com/treasure-data/digdag/commit/dbc12e40fc86a3a0f0552a921b380c0f9dd55b72#diff-828f306a0ac2fd6cd570c28c4b2f1cd2 > yoyama 17:54 The document is misleading. The description only focus when attempt already exists. If no attempt for the session time, require> always kick the child...

document