Update readmes for the 2022-06-02-preview dev branch of container service #19422
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
|
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 |
1 similar comment
|
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 |
Swagger Validation Report
|
Swagger Generation Artifacts
|
This was referenced Jun 13, 2022
FumingZhang
requested review from
msyyc,
BigCat20196,
ArcturusZhang,
palma21 and
matthchr
as code owners
moreOver0
approved these changes
Jun 13, 2022
FumingZhang
merged commit 7896acf
into
Azure:dev-containerservice-Microsoft.ContainerService-2022-06-02-preview
honghr
pushed a commit
that referenced
this pull request
Jul 20, 2022
…02-preview (#19653) * Adds base for updating Microsoft.ContainerService from version preview/2022-05-02-preview to version 2022-06-02-preview * Updates readme * Updates API version in new specs and examples * update readmes (#19422) * Containerservice 2022 06 02 preview fleet (#19541) * add fleets and fleet members resource types * remove clusterLocation * wording * don't flatten hubprofile * extra comma * fix patch example * Fix violated rule R4041 for 2022-06-02-preview managedCluster swagger (#19582) * remove useless directive * fix R4041 * fix * add node restriction to swagger (#19587) * aks fleet list credentials api (#19559) * add fleet list credential api * tweaks * fix example filename * fix casing * add resourceId on hubProfile * drop the new field, keep it as internal field * fix duplicate shema error * different name for fleet credential results * use xms-identifier on the array items * prettier fi Co-authored-by: Stephane Erbrech <stephane.erbrech@gmail.com> * sterbrec - address fleet comments - Microsoft.ContainerService - 2022-06-02-preview (#19783) * address fleet comments * add example for nadditional status code * Add missing `x-ms-long-running-operation-options` for delete operations in fleet-related API (#19787) * add final-state-via * fix final state to location header Co-authored-by: Stéphane Erbrech <stephane.erbrech@gmail.com> Co-authored-by: lht6 <46062996+lht6@users.noreply.github.com> Co-authored-by: Haitao Chen <haitch@users.noreply.github.com>
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.
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 appy to the PR so that the label "ARMReview" and "WaitForARMFeedback" will be added by bot to kick off ARM API Review. Missing to check this box in the following scenario may result in delays to the ARM manifest review and deployment.
-[ ] To review changes efficiently, ensure you are using OpenAPIHub to initialize the PR for adding a new version. More details, refer to the wiki.
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.