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

Exit Code is 0 when up fails #314

Closed
SteinRobert opened this issue Jan 12, 2023 · 0 comments · Fixed by #315
Closed

Exit Code is 0 when up fails #314

SteinRobert opened this issue Jan 12, 2023 · 0 comments · Fixed by #315
Labels
bug 🐛 Something isn't working

Comments

@SteinRobert
Copy link
Contributor

What happened?

When up fails the cli exits with 0.

What did you expect to happen?

It should exit with a code != 0.

How can we reproduce it (as minimally and precisely as possible)?

Run gefyra up --host not.reachable.

What Kubernetes setup are you working with?

$ kubectl version
# paste output here

OS version

# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here

# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here

Anything else we need to know?

No response

@SteinRobert SteinRobert added the bug 🐛 Something isn't working label Jan 12, 2023
SteinRobert added a commit that referenced this issue Jan 12, 2023
Signed-off-by: Robert Stein <robert@blueshoe.de>
Schille added a commit that referenced this issue Jan 13, 2023
SteinRobert added a commit that referenced this issue Jan 13, 2023
Minikube profiles and exit code fix for failed `up`
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug 🐛 Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant