Update readmes for the 2022-02-02-preview dev branch of container service #17889
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
FumingZhang
requested review from
msyyc,
BigCat20196 and
ArcturusZhang
as code owners
|
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. [email protected] |
|
[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 Generation Artifacts
|
This was referenced Feb 17, 2022
|
Hi @chunyu3, could you please help merge this PR? The PR only modifies the readme files and targets to a dev branch. |
chunyu3
reviewed
Feb 24, 2022
| @@ -400,6 +401,19 @@ input-file: | |||
|
|
|||
| ``` | |||
|
|
|||
| ### Tag: package-2022-02-02-preview-only | |||
There was a problem hiding this comment.
Why define this tag since there is already tag package-preview-2022-02? If you want to add directive for python SDK, you can add it in readme.python.md
There was a problem hiding this comment.
Hi @chunyu3, for a long time, container service has always had two sets of api tags, normal (package-xxx) and only (package-xxxx-only).
For the normal one (which is also the default tag and used by java/golang), it should also include several sets of old swagger (e.g. 2019-08-01/location) but I found that these two swagger files have a conflict on a query parameter named "ResourceTypeParameter" due to AutoRest v2 not supporting the same but not identical model definition. Our team will discuss about how to resolve the conflict. But for now we will keep only one swagger file included.
For the only one (which has directive definition and only used by python), it only includes the new swagger (e.g. xxxx/managedCluster).
Could you please help take another review and merge this PR? Thanks!
|
Hi @FumingZhang, Your PR has some issues. Please fix the CI sequentially by following the order of
|
openapi-pipeline-app
bot
added
CI-BreakingChange-JavaScript
CI-BreakingChange-Go-V2
and removed
CI-BreakingChange-Python-Track2
labels
FumingZhang
force-pushed
the
fuming/update-readme-cs-2022-02-02-preview
branch
from
cba5acc to
87c80be
Compare
chunyu3
approved these changes
Mar 3, 2022
chunyu3
merged commit 5d90509
into
Azure:dev-containerservice-Microsoft.ContainerService-2022-02-02-preview
jianyexi
pushed a commit
that referenced
this pull request
Mar 21, 2022
…02-preview (#18150) * Adds base for updating Microsoft.ContainerService from version preview/2022-01-02-preview to version 2022-02-02-preview * Updates readme * Updates API version in new specs and examples * Add key management service profile of a managed cluster for version 2022-02-02-preview (#17955) * Add key management service profile of a managed cluster for version 2022-02-02-preview * add kmsProfile * update after api review * add more details in description * update for comments * add mc snapshot api (#17974) * add mc snapshot api * fix format * add mc snapshot type * define type for enums * add properties for example * Update readmes for the 2022-02-02-preview dev branch of container service (#17889) * update readme * remove useless -only tags * remove nested property in allOf for 2022-02-02-preview managedClusters (#18063) * Fix credential format typo in 0102 preview (#18117) * add missing type object (#18116) * Update several common definitions according to arm feedback for container service 2022-02-02-preview (#18206) * update definition of serveral parameters and system data * update definition of Resource and move property location to sub resources * add missing tags property for prev Resource * fix for compatibility * fix definition name Co-authored-by: Bin Xia <[email protected]> Co-authored-by: Qingqing <[email protected]> Co-authored-by: Tongyao Si <[email protected]>
FredericHeem
pushed a commit
to grucloud/azure-rest-api-specs
that referenced
this pull request
May 16, 2022
…02-preview (Azure#18150) * Adds base for updating Microsoft.ContainerService from version preview/2022-01-02-preview to version 2022-02-02-preview * Updates readme * Updates API version in new specs and examples * Add key management service profile of a managed cluster for version 2022-02-02-preview (Azure#17955) * Add key management service profile of a managed cluster for version 2022-02-02-preview * add kmsProfile * update after api review * add more details in description * update for comments * add mc snapshot api (Azure#17974) * add mc snapshot api * fix format * add mc snapshot type * define type for enums * add properties for example * Update readmes for the 2022-02-02-preview dev branch of container service (Azure#17889) * update readme * remove useless -only tags * remove nested property in allOf for 2022-02-02-preview managedClusters (Azure#18063) * Fix credential format typo in 0102 preview (Azure#18117) * add missing type object (Azure#18116) * Update several common definitions according to arm feedback for container service 2022-02-02-preview (Azure#18206) * update definition of serveral parameters and system data * update definition of Resource and move property location to sub resources * add missing tags property for prev Resource * fix for compatibility * fix definition name Co-authored-by: Bin Xia <[email protected]> Co-authored-by: Qingqing <[email protected]> Co-authored-by: Tongyao Si <[email protected]>
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 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.
-[ ] 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.