Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

stdin for consul exec doesn't work on windows #1924

Closed
jirkafajfr opened this issue Apr 6, 2016 · 2 comments
Closed

stdin for consul exec doesn't work on windows #1924

jirkafajfr opened this issue Apr 6, 2016 · 2 comments
Labels
type/bug Feature does not function as expected

Comments

@jirkafajfr
Copy link

I am running following configuration:

  • chf01-pmtrm05 - consul 0.6.4 / CentOS 7.2
  • chf01-pmweb20 - consul 0.6.4 / Windows Server 2012 R2
echo 'echo Hi' | consul exec -
    chf01-pmtrm05: Hi
    chf01-pmtrm05:
==> chf01-pmtrm05: finished with exit code 0
    chf01-pmweb20: 'C:\Users\vagrant\AppData\Local\Temp\rexec223480077' is not recognized as an internal or external command,
    chf01-pmweb20: operable program or batch file.
    chf01-pmweb20:
==> chf01-pmweb20: finished with exit code 1

windows version is trying to execute name of key instead of command itself

@slackpad slackpad added the type/bug Feature does not function as expected label Apr 25, 2016
@slackpad slackpad added this to the 0.7.4 milestone Nov 22, 2016
@slackpad slackpad removed this from the Triaged milestone Apr 18, 2017
@slackpad
Copy link
Contributor

Closing this against #2999.

@slackpad
Copy link
Contributor

slackpad commented Oct 5, 2017

The stdin version still does shell escaping, but as of #3509 you can pass -shell=false to consul exec to get it to pass your arguments without any shenanigans.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/bug Feature does not function as expected
Projects
None yet
Development

No branches or pull requests

2 participants