rollback get_config_parser for backward compatibility#205
Merged
Conversation
arrownj
changed the title
jiasli
approved these changes
May 9, 2020
haroldrandom
approved these changes
May 9, 2020
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
3 participants
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.
In previous PR,
get_config_parserwas removed because packagesixwas removed and we can useconfigparser.ConfigParserdirectly. All previousget_config_parserinazure-cliare updated. However there is some extension which is not owned by CLI team (such as azure-devops) still use this function.For compatibility concern, it's better to keep this simple function.