Bilge
Bilge2mo ago

How do I act on the exit code of a previous flow step?

I cannot see any support for exit codes whatsoever, which seems like a huge omission, unless I'm missing something. Moreover, if I write a simple inline Bash step that just contains exit 1, the flow proceeds to the next step, reporting success. This is not at all what I expect.
6 Replies
Bilge
BilgeOP5w ago
The manual even has a section on error handling but seemingly never defines what an error is in the context of Windmill. Clearly it is not a non-zero status code, like it is in the rest of Unix-land
rubenf
rubenf5w ago
I just fixed the issue with exit 1 not being correctly propagated as an error in bash it was a regression related to a recent improvement with reaping background process
Bilge
BilgeOP5w ago
And hopefully tested so it doesn't regress again, right? 😆 I imagine it would seriously screw up some flows As to the material part of the question, is it possible to act on the status code (not just zero and non-zero, but capturing the specific code if desired)? If not, I'll file a feature request
rubenf
rubenf5w ago
we propagate exit_code as a field of the error
rubenf
rubenf5w ago
No description
Bilge
BilgeOP5w ago
Alright I guess I'll just wait for the fix to be tagged so I can play with this Which I see you just did 👌🏻