Argo: Per template exit handler.

Created on 12 Jul 2018  路  11Comments  路  Source: argoproj/argo

FEATURE REQUEST: Per template exit handler.

Hi,

Could it be possible to have a per-template exit handler, instead of having a single exit handler per workflow?

Here is a couple use cases:

  • We have a large workflow organized in templates, each executing a list of containers. Each template has its own clean up operations (e.g. terminate a Spark cluster that the template needed). These operations are not relevant to the other templates.

  • We want to compose workflows. Workflow 1 has an exit handler. Workflow 2 has an exit handler. When we programatically merge the workflows, there is no easy way to merge the workflow-level exit handlers.

enhancement

Most helpful comment

Fixed in #1716.

All 11 comments

/cc @qimingj

This would be really nice. For example, running a CD pipeline where at certain points the rollback situation is different.

+1
I have a couple of similar use cases for variable cleanup behaviour, and even just specialising error notifications to our Slack channel announcing the state of the pipeline after certain failure conditions.

+1. Any progress on this?

+1.

+1

+5000

Dear Argo, would love it if this feature is included in the roadmap.

It really enchance managing workflow

+1 Is this on the roadmap?

Looks like this is tracking in #1688

Looks like this is tracking in #1688

More specifically, https://github.com/argoproj/argo/pull/1716

Fixed in #1716.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

alexlatchford picture alexlatchford  路  3Comments

hden picture hden  路  3Comments

iterion picture iterion  路  3Comments

basanthjenuhb picture basanthjenuhb  路  3Comments

0xdevalias picture 0xdevalias  路  3Comments