Just for the record. Thanks to @carstenhaubold there is a Python based approach of executing bash commands.
Totally agree, we should make the External Tool node more usable.
Still, to give you a possible workaround right now, I just rebuilt the NGS Bash node’s functionality using the Python Script node in KNIME 4.7, and using the bundled Python environment (which it’ll use by default if you freshly install the Python Integration in KNIME). So you don’t even need to deal with setting up a Python installation.
Place a Python Script node in your workflow, click the three dots to remove the input table …
Unfortunately, though, it has the same issue that some commands are not found. That pretty much makes it abundantly clear that the PATH variable difference between Knime / Eclipse and vs. user under which it runs is at fault.
Bug Report
Hi,
for quite some time, interrupted by the sudden decommissioning of NGS (in particular the Bash Node), I attempted to resolve an issue in details explored in:
https://forum.knime.com/t/bash-node-command-not-found/46256
In a nutshell
Executing external commands only partially works (i.e. ping, nc) whilst other commands are not found
Using Python or Java to execute shell commands resulted in the same issue
Checking the Path variable indicates that Knime / Eclipse is not using the users Path…