[Log] Print INFO log from SDK#221
Merged
jiasli merged 8 commits intomicrosoft:masterfrom Dec 17, 2020
Merged
Conversation
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Collaborator
|
Log |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Previously in
get_logger, logger name is the module name prefixed withCLI_LOGGER_NAME, likecli.azure.cli.core. Now it only takes the module name, likeazure.cli.core, to be in sync with the Python SDK's logger nameazure.*.Make
cli_logger_namecustomizable, so that allINFOlogs underazure.*loggers can be printed, likeazure.core.pipeline.policies.http_logging_policyazure.cli.corePreviously, logger
cli.azure.cli.core's logger name is not printed:Now the logger name is printed even for CLI logger when
--debugis specified, so that the log source can be better distinguished.ℹ As before,
DEBUGlog from both CLI and underlying libs will be printed, so this won't affectDEBUGlog.Example: