Support non-Bash shells (tcsh/csh) on remote hosts in SSH deployments
Q
Qualified Canidae
When executing Command or Shell Script steps on a remote host via SSH, Harness uses the default shell of the target machine and its internal wrapper script assumes Bash syntax. If the remote host's default shell is tcsh or csh, both the wrapper and user scripts fail with unclear errors ("Command not found", "Undefined variable"). Shebangs do not override this behavior.
Request:
- Add support for non-Bash shells (tcsh, csh, ksh) on remote SSH targets, or invoke Bash explicitly regardless of the host's default shell.
- If a target shell is unsupported, fail with a clear error message stating the shell is not supported rather than producing misleading errors.
Log In