A new option (--correct-command) in check-tools script allows to remove automatically the use of $__tool_directory__ macro inside the command tag of XML tool files. The use of that command prevents the tool's container from running in Galaxy/Kubernetes.
I totally agree flagging $__tool_directory__ as a problem when found. Maybe automatically editing the file is a little too ambitious? Would the code would be able to ensure the edited path is indeed valid?
A new option (
--correct-command
) incheck-tools
script allows to remove automatically the use of$__tool_directory__
macro inside the command tag of XML tool files. The use of that command prevents the tool's container from running in Galaxy/Kubernetes.