-
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
Dev kubernetesconfiguration microsoft.kubernetes configuration stable 2021 03 01 #12500
Dev kubernetesconfiguration microsoft.kubernetes configuration stable 2021 03 01 #12500
Conversation
… preview/2020-10-01-preview to version 2021-03-01
Hi, @NarayanThiru 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 |
Swagger Validation Report
|
Swagger Generation Artifacts
|
Hi, @NarayanThiru your PR are labelled with WaitForARMFeedback. A notification email will be sent out shortly afterwards to notify ARM review board(armapireview@microsoft.com). cc @ |
@jianyexi, this PR is to create a new api-version for our upcoming GA release. Compared to our most recent Public Preview api-version 2020-10-01-preview, there are no changes - except a Swagger Linting fix. Please help us get this merged at the earliest possible. |
Ok, needs ARM review first. |
@jianyexi, ARM team has signed off. Can you please help get this merged? |
...rce-manager/Microsoft.KubernetesConfiguration/stable/2021-03-01/kubernetesconfiguration.json
Outdated
Show resolved
Hide resolved
Hi @NarayanThiru, Your PR has some issues. Please fix the CI sequentially by following the order of
|
… 2021 03 01 (Azure#12500) * Adds base for updating Microsoft.KubernetesConfiguration from version preview/2020-10-01-preview to version 2021-03-01 * Updates readme * Updates API version in new specs and examples * Fixed review comment * Fixed reference path error * Fixed casing error in enum
MSFT employees can try out our new experience at OpenAPI Hub - one location for using our validation tools and finding your workflow.
Changelog
Please ensure to add changelog with this PR by answering the following questions.
During Ignite conference - around 02 March, 2021.
As soon as the Swagger is merged, this week, if possible.
Since this is a new api-version, we need SDKs generated
Contribution checklist:
If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist
Ensure to check this box if one of the following scenarios meet updates in the PR, so that label “WaitForARMFeedback” will be added automatically to involve ARM API Review. Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs, all “removals” and “adding a new property” no more require ARM API review.
- Adding a new API version
Please 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 there are following updates in the PR, ensure to request an approval from API 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.