Skip to content

Conversation

@derekbekoe
Copy link
Member

No description provided.

@azurecla
Copy link

azurecla commented Aug 1, 2016

Hi @derekbekoe, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no contribution license agreement is required at this point. Real humans will now evaluate your PR.

TTYL, AZPRBOT;

Copy link
Contributor

@yugangw-msft yugangw-msft Aug 1, 2016

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i like this change personally, but for the people get used to interactive flow, is it possible we can still output the starting message, but just don't prefix with "warning:"?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

'WARNING:' is not displayed in interactive mode (if there's a TTY available).
But log message are prefixed with the log level if there is no TTY (e.g. redirecting the output to file) as was the case in #572.

@tjprescott
Copy link
Member

:shipit:

@yugangw-msft yugangw-msft merged commit 130b05d into Azure:master Aug 2, 2016
@derekbekoe derekbekoe deleted the lro-no-log branch August 2, 2016 16:21
00Kai0 pushed a commit to 00Kai0/azure-cli that referenced this pull request Apr 7, 2021
00Kai0 pushed a commit to 00Kai0/azure-cli that referenced this pull request Apr 7, 2021
* Fixes Azure#591.

* Update index for ER cross connection

* Fix linter violations.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants