-
Notifications
You must be signed in to change notification settings - Fork 5.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
extract SkuTier as seperate definition for common-types/v3.json #15898
Conversation
Hi, @zhenglaizhang Thanks for your PR. I am workflow bot for review process. Here are some small tips. Any feedback about review process or workflow bot, pls contact swagger and tools team. vsswagger@microsoft.com |
[Call for Action] To better understand Azure service dev/test scenario, and support Azure service developer better on Swagger and REST API related tests in early phase, please help to fill in with this survey https://aka.ms/SurveyForEarlyPhase. It will take 5 to 10 minutes. If you already complete survey, please neglect this comment. Thanks. |
Swagger Validation Report
|
Swagger pipeline restarted successfully, please wait for status update in this comment. |
This will address the issue in #15662, so thank you. I just wanted to also point out that this same type of change could be applied to the other enum property types, as well. like "type", "origin", "actionType", "createdByType", "lastModifiedByType", "status", and "reason". |
@zhenglaizhang Do you need review from ARM? |
@msyyc @qiaozha @fengzhou-msft @ArcturusZhang could you help take a look from SDK perspective? |
One question not related to this change. Why use "allOf"? azure-rest-api-specs/specification/common-types/resource-management/v3/types.json Lines 169 to 189 in 4749798
|
no need to do ARM review, |
good catch, ref should be better here. |
.net/python sdk owners are also ok with this change. |
@forteddyt I merged the PR, so you can try to reference it in v3 common types.json |
This is per request from service team (#15662 (comment)) and I did a check on python track2 it's not a breaking change in PR #15876.
And need SDK owners review to check if it's a SDK breaking change