Repository navigation
Pipes not working in @actions/exec node module #359
Description
Describe the bug
It looks like @actions/exec.exec escapes commands and pipes are not working because of this
To Reproduce
Steps to reproduce the behavior:
- Create a new javascript action
- Add
@actions/execto project -npm i -s @actions/exec - In your index file add any .exec command with pipe, ie:
echo "Hello world" | grep "o" - It would print
Hello world" | grep "o", instead ofHell**o** w**o**rld(asterisks here are only for visual purpose, i do not expect them to be in log)
Expected behavior
Have an option to disable escaping
Screenshots
Desktop (please complete the following information):
- OS: tested on macOS-latest machine
- Browser [e.g. chrome, safari]
- Version @actions/exec@1.0.3
Reacted by Denis Tuzhik, Kamil Szubrycht, Hannes Rüger, Zach Guo, Stefan Buck, Juan Andrés Zeni, Rick Staa and Thiago da Silva
Activity
hrueger commentedon Mar 24, 2020
@Kerizer I have the same problem, the command I want to run is
yes | sdkmanager --licensesto automatically accept all prompts withyes. This does not work, it takes| sdkmanager --licensesas one argument and prints that forever until I cancel the workflow.A workaround I found is to use
/bin/bash -c "my command", e.g./bin/bash -c "yes | sdkmanager --licenses". That worked for me.hrueger commentedon Mar 25, 2020
As I just found out, this also affects chaining commands with
&&...rickstaa commentedon Dec 12, 2020
@hrueger Thanks a lot for the workaround. For future reference here is the windows equivalent:
WINDOWS:
thboop commentedon Apr 29, 2021
Closing as a dupe of #346
https://github.com/actions/toolkit/issues/359