You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This Allowed the user to select which steps to reset as part of the Retry command.
I think we can use the restartSuccesful property that was added to allow rerunning successful workflow from given steps.
Use Cases
I created a mechanism for rerun with debug pause (in short: all templates have the env variable ARGO_DEBUG_PAUSE_{{workflow.parameters.pause}}, the default value for pause is NEVER, when I use the Retry I override the value to AFTER).
I want to be able to use it also for successful workflows (for instance: I need to do manual operation on terraform state, I need to test out something manually etc etc).
Implmentation
The Retry operation will fail if workflow is not in Failed or Error state:
Summary
restartSuccesful
property that was added to allow rerunning successful workflow from given steps.Use Cases
ARGO_DEBUG_PAUSE_{{workflow.parameters.pause}}
, the default value for pause isNEVER
, when I use the Retry I override the value toAFTER
).Implmentation
The Retry operation will fail if workflow is not in Failed or Error state:
argo-workflows/workflow/util/util.go
Line 806 in ec85683
IIUC, it should be fairly simple to change this condition to allow other states, in case the
restartSuccesful
and node selector were given.WDYT?
cc: @markterm
Message from the maintainers:
Love this enhancement proposal? Give it a 👍. We prioritise the proposals with the most 👍.
The text was updated successfully, but these errors were encountered: