Can we use bash for custom workflow's run step?

[qingvincentyin]

It appears that the run step in a custom workflow is using the Bourne shell (/bin/sh) rather than bash.

Is there a way to tell custom workflow's run step to use bash?

(I suppose I can do /bin/bash -c ... as an indirection, but then I'd have to worry about escaping special characters, etc. It'll be a lot easier if I can just write in straight bash syntax.)

---

UPDATE 6 months later: Some workarounds...

Extend this base Docker image (therefore run our own custom image for Atlantis in Kubernetes). Copy our own bash custom shell script (say, /.../my_bash_script.sh) into the new image, or alternatively, mount a volume (containing my_bash_script.sh) to the image/pod. Then, from Atlantis run step, we could do /bin/bash /.../my_bash_script.sh
.

[bogdan-rizac]

@lkysow any answer on this ? At least an idea on how to switch to bash would be great

[nitrocode]

@qingvincentyin @bogdan-rizac

You folks can use any shell you like by cutting your own image and installing it.

RUN apk add bash

You can then run a script in a custom workflow and use a shebang like this

#!/usr/bin/env bash

[nitrocode]

If you'd like to change the interpreter, someone could add a new flag that defaults to sh and passes the flag to each of these places.

https://github.com/search?q=repo%3Arunatlantis%2Fatlantis+exec.Command%28%22sh%22%2C&type=code&l=Go

Please feel free to contribute a new change.

The easier method would be to write a shell script, set the interpreter using the shebang, and run it using the run step.

[bml1g12]

If you'd like to change the interpreter, someone could add a new flag that defaults to sh and passes the flag to each of these places.

https://github.com/search?q=repo%3Arunatlantis%2Fatlantis+exec.Command%28%22sh%22%2C&type=code&l=Go

Please feel free to contribute a new change.

The easier method would be to write a shell script, set the interpreter using the shebang, and run it using the run step.

Sadly I don't think the "easier method" works:

with test.sh

#!/usr/bin/env bash
set -Eeuxo pipefail
set +o pipefail
set +x
echo $0
echo "hello"  |& tee -a test.log

cat test.sh | sh

03955a7d9e3a:/mount# cat test.sh | sh 
+ set +o pipefail
+ set +x
sh
sh: syntax error: unexpected "&"

Expected output:

03955a7d9e3a:/mount# cat test.sh | bash
+ set +o pipefail
+ set +x
bash
hello