{AppConfig} Migrate to Track 2 Mgmt SDK #16376
Merged
Conversation
This file contains 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
|
@shenmuxiaosen can you please help review these changes? |
|
AppConfig |
|
@avanigupta I am writing a document of how to migrate to Track 2 SDK. You are welcome to contribute to it. |
qwordy
approved these changes
Dec 29, 2020
qwordy
approved these changes
Dec 29, 2020
3 tasks
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.
Description
This PR upgrades the azure-mgmt-appconfiguration library to version 1.0.1, which is the new track 2 management plane SDK.
Changes in Track 2 SDK:
ErrorExceptionhas been removed. The SDK now throwsHttpResponseErrorinstead.begin_.idcannot be passed directly toregenerate_keymethod. It needs to be wrapped in the new modelRegenerateKeyParameters.ApiKeyobject, which does not need to be converted to JSON object.Testing Guide
History Notes
This checklist is used to make sure that common guidelines for a pull request are followed.
The PR title and description has followed the guideline in Submitting Pull Requests.
I adhere to the Command Guidelines.
I adhere to the Error Handling Guidelines.