{ARM} Bump azure-mgmt-resource from v2019-07-01 to v2020-06-01#14344
{ARM} Bump azure-mgmt-resource from v2019-07-01 to v2020-06-01#14344
Conversation
|
add to S173 |
80a33c2 to
ec4016c
Compare
ca579f1 to
ebcd759
Compare
There was a problem hiding this comment.
Is it a breaking change?
There was a problem hiding this comment.
Yes, it is a breaking change of SDK, and we did made some compatibility logic to ensure that the CLI will not be broken
3f167be to
aac6ad8
Compare
47b21b8 to
2374d54
Compare
There was a problem hiding this comment.
Compatibility logic for breaking change from SDK
mmyyrroonn
left a comment
There was a problem hiding this comment.
Approved for monitor commands
Juliehzl
left a comment
There was a problem hiding this comment.
approve for storage part
d7b4f58 to
515ac0d
Compare
arrownj
left a comment
There was a problem hiding this comment.
For VM module, it's good.
|
@samkreter Could you please help to review this PR for your part~ |
There was a problem hiding this comment.
Does this comments affect test result? #Closed
There was a problem hiding this comment.
This is automatically generated and should not affect the test results #Closed
b5dde9b to
3f120b8
Compare
3f120b8 to
a043ea6
Compare
|
/azp run |
|
Azure Pipelines successfully started running 2 pipeline(s). |
Description
Bump azure-mgmt-resource from v2019-07-01 to v2020-06-01
For PR: #13429 #14241
At the same time, some compatibility logic was made for the breaking change of SDK to ensure that breaking will not be produced on the CLI side, such as: click
Testing Guide
History Notes
[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change.
[Component Name 2] az command b: Add some customer-facing feature.
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.