argoproj / argoproj/argo-workflows
Add workflow events for suspended nodes
- Dominant language
- Go
- Stars
- 17k
- Forks
- 3.7k
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 138
Description
# Summary
Currently there are `node completion` events https://github.com/argoproj/argo/blob/master/docs/workflow-events.md:
* `WorkflowNodeSucceeded`
* `WorkflowNodeFailed`
* `WorkflowNodeError`
This proposal is to add an additional one for `WorkflowNodeSuspended`
# Use Cases
This would be used for an application that is managing the suspended nodes and responsible for resuming them.
---
**Message from the maintainers**:
Impacted by this bug? Give it a 👍. We prioritise the issues with the most 👍.
Contributor guide
Research direction
Start by reading docs/workflow-events.md and tracing how the existing WorkflowNodeSucceeded, WorkflowNodeFailed, and WorkflowNodeError events are defined and emitted. Confirm the suspended-node lifecycle and its tests before making the change. Done means WorkflowNodeSuspended is emitted for suspended nodes and documented alongside the existing node completion events.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100