argoproj / argoproj/argo-workflows
`when` for output artifacts
- Dominant language
- Go
- Stars
- 17k
- Forks
- 3.7k
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 138
Description
# Summary
Ability to optionally output artifacts, just like `dag` or `steps` `when`.
# Use Cases
A validation pipeline running on `main` needs to upload artifacts whereas other branches do not.
---
**Message from the maintainers**:
Love this enhancement proposal? Give it a 👍. We prioritise the proposals with the most 👍.
Contributor guide
Research direction
Compare how conditional `when` works for `dag` and `steps` with the output-artifact behavior described here. Trace the workflow artifact handling entry points and define done as allowing artifacts to be uploaded conditionally, such as only on `main`, without changing unconditional artifact behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100