Enhance error management
mudler opened this issue · comments
Currently yip returns error dynamically. This makes things like rancher/elemental-toolkit#1109 difficult to achieve, as there is no way to check what kind of error was generated from yip.
Action items
- Identify type of errors
- Define statically errors so they can be checked out downstream
- Consume the static errors in the code
I've been just checking out this. Seems we do just wrap errors on executors and do not create really new, except in the plugins. this might not be required at the end.
Seems it's not required. yip doesn't create new errors while unmarshalling and executing steps, but just wraps them. The only area of code that are generating new errors is the one about plugins, but those should be implemented on a need-basis, as there are no real common errors between them