-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Add support for docker push --quiet #2197
Conversation
Signed-off-by: Justyn Temme <justyntemme@gmail.com> Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
ping @silvin-lubecki @kolyshkin PTAL |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Completion LGTM.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
yeet |
@@ -66,5 +68,9 @@ func RunPush(dockerCli command.Cli, opts pushOptions) error { | |||
} | |||
|
|||
defer responseBody.Close() | |||
return jsonmessage.DisplayJSONMessagesToStream(responseBody, dockerCli.Out(), nil) | |||
if !opts.quiet { | |||
return jsonmessage.DisplayJSONMessagesToStream(responseBody, dockerCli.Out(), nil) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like actual push errors are produced here, so skipping this caused errors to not be printed, and docker push
_always returning a zero-status exit code ("success") when using --quiet
See #2284
Coming in 20.03.0 - see docker/cli#2197
- Description for the changelog
+ Add support for docker push --quiet
- A picture of a cute animal (not mandatory but encouraged)