argoproj / argoproj/argo-workflows
Configure memoization storage at spec level
- Dominant language
- Go
- Stars
- 17k
- Forks
- 3.7k
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 138
Description
# Summary
Currently memoization storage is configured at step level. Configuring at workflow level would be more user friendly.
# Motivation
To reduce time and effort configuring memoization.
# Proposal
`/spec/memoization/cache` or similar.
---
**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
Start by reading how memoization storage is currently configured at the step level and how workflow specifications are structured. Define the proposed spec-level location, such as /spec/memoization/cache, and confirm that configuring it at workflow level reduces repeated step configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- backend, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100