Closed gggeek closed 4 years ago
Point A implemented in 5.13.
It is now possible to make migrations abort if the external process returns non-zero via element fail_on_error
.
About fail on stderr non empty
: this can be done, albeit in a more clumsy way: set a ref to stderr, then add a fail step if that is empty. I think this is an acceptable compromise as it should not be a very frequent requirement.
About point B: it will be implemented separately
a) it should be easier to tag a migration failed if the process exited as non-0, with anything written to stdout, or both. At the moment, we just swallow it all...
b) add to the docs a couple of examples of setting refs to the output and dealing with it