-
Notifications
You must be signed in to change notification settings - Fork 224
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
Fail "build" if Docker CLI throws an error #138
Comments
I’ll give this one a shot 🙌🏼🙌🏼 |
Please provide output from testing in the PR (positive and negative) along with what happens if you have multiple functions or a single. GIFs are also very good for showing new behavior. Looking forward to seeing this. |
So it seems the only way to get the error status is in ExecCommand(), would you like to handle any errors there? The push command also utilizes ExecCommand() so that might be the best option. |
I think you can check for Exit code on the command object |
Fixed in 139. With some notes on a v2 implementation. |
Expected Behaviour
We need to "stop the world" if a
faas-cli build
throws an error.Current Behaviour
Error is swallowed and hard to see.
Possible Solution
At the least just
log.Fatal()
and emit non-zero exit code.Better - print a message in red with the aec library we use for "version"/"new" commands.
Steps to Reproduce (for bugs)
Use a Dockerfile with a bad instruction and do
faas-cli build
The text was updated successfully, but these errors were encountered: