[Proposal] Support resubmit/retry on archived workflows

[terrytangyuan]

Summary

What change needs making?

Support resubmit/retry on archived workflows.

Use Cases

When would you use this?

Currently argo retry/resubmit only supports workflows resources that currently exist in the cluster. For clusters where workflows are GC-ed immediately after they are completed, it's not possible to retry/resubmit a workflow. There are workaound for this, e.g. saving the workflow resource manually either as a plain YAML or into archived workflow before we GC it, and then do a kubectl create before we use argo retry/resubmit. It would be better and less hacky if we have a CLI for this.

API/Implementation Discussion

We can implement this in one of the following ways:

1. argo retry/resubmit wf-name --from-archive
2. argo archive retry/resubmit
3. argo retry/resubmit --source=location-to-saved-wf.yaml

Tasks

• Add Retry API on Archive workflow #7906
• Add Archive Retry Command on CLI #7907
• Add Retry Button on UI #7908
• Add Resubmit API on Archive workflow #7909
• Add Archive Resubmit Command on CLI #7910
• Add Resubmit Button on UI #7911

Any preference?

---

Message from the maintainers:

Impacted by this bug? Give it a 👍. We prioritise the issues with the most 👍.

[alexec]

We should also provide this feature in the UI. I'd split this into two issues:

• Support retrying archived workflows in UI and CLI
• Support resubmitting archived workflows in UI and CLI

[dpadhiar]

I will take this issue

[terrytangyuan]

Wow this got popular. 👍🏻 @dpadhiar assigned to you.