-
Notifications
You must be signed in to change notification settings - Fork 5.1k
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
Review request for Microsoft.ContainerService to add version 2022-02-01 #18324
Review request for Microsoft.ContainerService to add version 2022-02-01 #18324
Conversation
…/2022-01-01 to version 2022-02-01
…ure#17887) * update readme * remove useless -only tags
…18024) * fix allof * add missing type
* GA alias minor version * polish more details on kubernetesVersion and currentKubernetesVersion * Update specification/containerservice/resource-manager/Microsoft.ContainerService/stable/2022-02-01/managedClusters.json minor revision Co-authored-by: Matthew Christopher <matthchr@microsoft.com> Co-authored-by: Matthew Christopher <matthchr@microsoft.com>
This reverts commit 3a99cda.
…view for container service 2022-02-01 (Azure#18216) * sync modification * fix ref
Hi, @FumingZhang 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. vscswagger@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. |
Hi, @FumingZhang your PR are labelled with WaitForARMFeedback. A notification email will be sent out shortly afterwards to notify ARM review board(armapireview@microsoft.com). |
Swagger Generation Artifacts
|
Hi @FumingZhang, Your PR has some issues. Please fix the CI sequentially by following the order of
|
For the failures in Swagger Avocado, three of them are deprecated, The remaining one is the swagger file we are currently using and continuously updating, the latest version is |
@ruowan please help check the avocado error |
I checked the detail log. |
Hi ruowan, I've confirmed with feature owner that the path mentioned above is deprecated. |
…01 (Azure#18324) * Adds base for updating Microsoft.ContainerService from version stable/2022-01-01 to version 2022-02-01 * Updates readme * Updates API version in new specs and examples * Update readmes for the 2022-02-01 dev branch of container service (Azure#17887) * update readme * remove useless -only tags * Fix violated rule R2026 for 2022-02-01 managedCluster swagger (Azure#18024) * fix allof * add missing type * GA alias minor version (Azure#18038) * GA alias minor version * polish more details on kubernetesVersion and currentKubernetesVersion * Update specification/containerservice/resource-manager/Microsoft.ContainerService/stable/2022-02-01/managedClusters.json minor revision Co-authored-by: Matthew Christopher <matthchr@microsoft.com> Co-authored-by: Matthew Christopher <matthchr@microsoft.com> * add missing type object (Azure#18115) * Revert "GA alias minor version (Azure#18038)" (Azure#18291) This reverts commit 3a99cda. * Align modifications of several common definitions with 2022-02-02-preview for container service 2022-02-01 (Azure#18216) * sync modification * fix ref Co-authored-by: Jianping Zeng <zjpjack@users.noreply.github.com> Co-authored-by: Matthew Christopher <matthchr@microsoft.com>
MSFT employees can try out our new experience at OpenAPI Hub - one location for using our validation tools and finding your workflow.
Changelog
Add a changelog entry for this PR by answering the following questions:
Contribution checklist:
If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist
Otherwise your PR may be subject to ARM review requirements. Complete the following:
Check this box if any of the following apply to the PR so that label "WaitForARMFeedback" will be added automatically to begin ARM API Review. Failure to comply may result in delays to the manifest.
Ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.
If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
Breaking Change Review Checklist
If any of the following scenarios apply to the PR, request approval from the Breaking Change Review Board as defined in the Breaking Change Policy.
Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.