Good morning @gab1one,
the bash node getting remove, rendering workflows unusable after update (worth to note that downgrading is quite a pain), causing quite some discomfort to be honest.
Especially because the External Tool – KNIME Community Hub node being poorly implemented as it:
- Lacks support for path variables
- Not all input fields are able to get dynamically populated via flow variables
- Paths can’t be manually specified i.e. to be relative to workflow data directory
- Switching of input types (data vs variables) is impossible
- Usage of the external tools required to generate (manually or via knime) a bash script and make it executable
Generally speaking, the external tool node profoundly blocks the dynamic usage of knime. The node usage feels rather restrictive and not well integrated.
I apologize for the rather blunt but only aim to provide a constructive as possible feedback. Especially as the node got removed without any advance warning time like being marked as deprecated first, then marked as to be removed with clear visual change and / or warning upfront.
@ipazin once mentioned that deprecated nodes are not causing much of a problem and simply stay there. Though, the sudden removal, form my perspective, reveals the necessity of a more well informed and managed deprecation / removal process to omit workflows breaking without warning.
Kind regards
Mike