argoproj / argoproj/argo-workflows
Unify DAGTask and WorkflowStep
- Dominant language
- Go
- Stars
- 17k
- Forks
- 3.7k
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 138
Description
FEATURE REQUEST
It would be great if DAGTask and WorkflowStep were merged to become a single `Task` API type. (Similar to k8s' PodSpec that is used in both Pods ind Jobs).
The only difference right now (apart from different language in descriptions) is the `dependencies` property. We could just say that in `steps` context the `dependencies` also exist, but are populated automatically.
Contributor guide
Research direction
The issue names DAGTask, WorkflowStep, Task, and the dependencies property, but it does not identify files, tests, or entry points. Start by locating the definitions and their uses, then clarify how a unified API should represent automatically populated dependencies and how compatibility will be verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100