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

Get non-zero exit code from sonnobuoy cli in case of returned failed status #404

Closed
mwieczorek opened this issue Mar 29, 2018 · 0 comments · Fixed by #463
Closed

Get non-zero exit code from sonnobuoy cli in case of returned failed status #404

mwieczorek opened this issue Mar 29, 2018 · 0 comments · Fixed by #463
Labels
kind/bug Behavior isn't as expected or intended lifecycle/active Actively being worked on p1-important

Comments

@mwieczorek
Copy link

Is this a BUG REPORT or FEATURE REQUEST?:
Feature Request

What happened:
I run:
sonobuoy status
and get information about failed plugin.
But when I run
echo $?
I got
0
exit code.

What you expected to happen:
If status is failed I'd like to get non zero exit code so I can handle it properly in case of using sonobuoy cli in bash scripts. Without it I need to parse the output.

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:
I run sonobuoy v0.11.1

Environment:

  • Sonobuoy tarball (which contains * below)
  • Kubernetes version (use kubectl version):
  • Cloud provider or hardware configuration:
  • OS (e.g. from /etc/os-release):
  • Kernel (e.g. uname -a):
@timothysc timothysc added kind/bug Behavior isn't as expected or intended p1-important labels Mar 29, 2018
@timothysc timothysc added this to the v1.0.0 milestone Mar 29, 2018
@timothysc timothysc assigned timothysc and unassigned liztio Jun 22, 2018
@timothysc timothysc modified the milestones: v1.0.0, v1.11-upstream sync Jun 22, 2018
@chuckha chuckha added the lifecycle/active Actively being worked on label Jul 3, 2018
@chuckha chuckha assigned chuckha and unassigned timothysc Jul 3, 2018
chuckha pushed a commit to chuckha/sonobuoy that referenced this issue Jul 3, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Behavior isn't as expected or intended lifecycle/active Actively being worked on p1-important
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants