Proposal: argo resubmit #694
Milestone
Comments
|
👍 Would be really good to have this feature. Any timeline planned for this feature? |
icecoffee531
pushed a commit
to icecoffee531/argo-workflows
that referenced
this issue
Jan 5, 2022
* fix: gateway and sensor service name * feat: added auto notification registration for storagegrid * feat: adding auto registration for storage grid * feat: auto notification configuration for storagegrid * chore: remove defunct test * chore: fix package name * chore: remove optional namespace
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
A common request/use case is to restart or resubmit a failed workflow, and reuse the progress which it already made, then retrying the failed steps and continuing where the workflow left off.
This proposal is for a
argo resubmit <workflowname>command. This would be an entirely client-side feature which would formulate a new workflow based upon a previous, completed workflow, by filling-out the node statuses with results from the previous run, such that once received, the controller would operate on the workflow as if it were in the middle of operation.The text was updated successfully, but these errors were encountered: