argoproj / argoproj/argo-workflows
Add `tasks.<TASKNAME>.podName` to DAG Templates
- Dominant language
- Go
- Stars
- 17k
- Forks
- 3.7k
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 138
Description
# Summary
Add `tasks..podName` to DAG Templates
Add `steps..podName` to Steps Templates
## Use Cases
1. The default key for artifact is `{{workflow.name}}/{{pod.name}}/< NAME >`. If it is added, then this key can be concatenated in other tasks.
2. other tasks need read pod name of previous task
---
**Message from the maintainers**:
Love this feature request? Give it a 👍. We prioritise the proposals with the most 👍.
Contributor guide
Research direction
The issue names no files or tests; start by locating how DAG and Steps templates expose task fields and how template variables are tested. Done means both task.podName and step.podName are available to other tasks for the stated artifact and dependency use cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- backend, distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100