Proposal: ability to specify default sh runner

[knutov]

Few weeks after #116 I came to those facts:

• some servers have sh to dash by default, some servers to bash
• dash and bash have incompatibilities, may be even in strict sh syntax
• dash is faster (some times x1.5..x2) but some code requires bash
• it is possible to specify interpreter in the shebang line
• but it takes one more line each task
• not possible to specify for short one-line commands
• behavior/result of task is unpredictable if interpreter is not set
• it is not possible to change sh to dash/bash on servers because of other software having some strict expectations

So, please, is it possible to add option "default interpreter"? With /bin/sh by default and possibility to set it to /bin/bash (or any other sh-compatible binary)

[umputun]

I have implemented it in PR #141

Pls give it a try and see if this is what you want. This change introduced a new --shell ($SPOT_SHELL) parameter allowing to set a default shell runner for remote operations.

if you don't know how to build this version, let me know what platform you need it, and I'll make a binary for you

[umputun]

see #151, in master

[knutov]

looks wonderful, thanks!

a little bit odd:

        script: |
          FILE_NAME=/tmp/file1
          touch $FILE_NAME
          ANOTHER_VAR=foo
        register: [FILE_NAME, ANOTHER_VAR]

is working, but

        script: FILE_NAME=/tmp/file1 ; touch $FILE_NAME ; ANOTHER_VAR=foo
        register: [FILE_NAME, ANOTHER_VAR]

is not working. This should be the almost the same data structure after parsing yaml, I thought.

[umputun]

This is sort of expected, at least technically. Such a single-line command doesn't make a script, and we have no place to add setvar thing. For export, it has a special logic to make a script even for single-line commands.

i don't have an easy solution for this limitation yet, need to think about it

[umputun]

found an easy way, should be on master

[knutov]

Thanks!