argoproj / argoproj/argo-workflows
Add "reason" parameter when terminating and resuming a Workflow
- Dominant language
- Go
- Stars
- 17k
- Forks
- 3.7k
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 138
Description
# Summary
Allow additional parameter when a workflow is terminated or resumed
## Use Cases
When a workflow is terminated by an external system, there is no indication on why it was terminated
Having some kind of additional data that could be show as an output parameter on the task where the workflow is suspended would enhance communication
---
**Message from the maintainers**:
Love this enhancement proposal? Give it a 👍. We prioritize the proposals with the most 👍.
Contributor guide
Research direction
Start by tracing the existing API entry points for terminating and resuming a Workflow, then follow how suspension and task output parameters are represented. Clarify how an external system supplies the reason and where it should appear when the workflow is suspended. Done means both operations accept the additional reason and the suspended task exposes it as output data.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100