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

consul kv get error goes to stdout instead of stderr #3100

Closed
cbednarski opened this issue Jun 1, 2017 · 2 comments
Closed

consul kv get error goes to stdout instead of stderr #3100

cbednarski opened this issue Jun 1, 2017 · 2 comments
Labels
waiting-reply Waiting on response from Original Poster or another individual in the thread

Comments

@cbednarski
Copy link

When I get an error from consul kv get the error is written to stdout, which means that the error text appears to be the data I asked for. The error should go to stderr instead so it not confused with data.

For example when wrapping consul with bash I not only have to check the exit code but I also need to replace the output value with some other value that is not invalid data. I also lose the error messages from logs because I am capturing stdout in a variable.

/cc @evanphx

@slackpad
Copy link
Contributor

slackpad commented Jun 1, 2017

@cbednarski this should be fixed by #2548 as of 0.8.0 - are you seeing this on the latest version of Consul?

@slackpad slackpad added the waiting-reply Waiting on response from Original Poster or another individual in the thread label Jun 1, 2017
@cbednarski
Copy link
Author

Oops, thanks for the details @slackpad! Looks like we're on 0.7.5. We'll update.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
waiting-reply Waiting on response from Original Poster or another individual in the thread
Projects
None yet
Development

No branches or pull requests

2 participants