How to let exit handler access stdout result and artifacts? #12969
Replies: 1 comment
-
In the end I didn't use the exit handler. I didn't get it to work and it was easier to just put those steps at the end of the DAG. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
This is a simplified version of what I'm trying to do. There might be a few yaml syntax errors in here, but that should not be an issue. Basically I have a dag workflow that creates multiple variants of raw input data. And when this is done, for each variant I want to send a message using an exit handler. To do that, I first need to build the message. And for that I need information and artifacts from the actual workflow. Even after looking into the documentation, I am pretty much confused how to do that. I marked the problematic spots in the exit handler with
<??? [...] ???>
Note: The real thing is much more complex ;-). Even if it looks like this could be separated into 2 separate workflow executions, in reality the variants kind of depend on each other. And dependent on the raw data (and a few other factors), later steps (variants) can fail. But that should not prevent from uploading the parts that were completed and send a notification for them. Again: this is a simplified version ;-)
Can someone please enlighten me how to get the required data into the exit handler tasks? :) (especially when using dag and multiple dag tasks which use the same task template).
Beta Was this translation helpful? Give feedback.
All reactions