argoproj / argoproj/argo-workflows
retryStrategy step/DAG task scoped
- Dominant language
- Go
- Stars
- 17k
- Forks
- 3.7k
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 138
Description
# Summary
Have `retryStrategy` step/DAG task scoped rather than template scoped.
# Motivation
Every step/DAG task using same template may require different `retryStrategy` .
# Proposal
N/A
---
**Message from the maintainers**:
If you wish to see this enhancement implemented please add a 👍 reaction to this issue! We often sort issues this way to know what to prioritize.
Contributor guide
Research direction
The issue mentions retryStrategy on step/DAG tasks and templates but names no files, tests, or entry points. Start by tracing where retryStrategy is defined and resolved for templates and task types, then determine the configuration and compatibility changes needed. Done means different tasks using the same template can apply different retry strategies, with coverage for both step and DAG tasks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100