-
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 desktopvirtualization microsoft.desktop virtualization 2022 02 02 preview #17660
Dev desktopvirtualization microsoft.desktop virtualization 2022 02 02 preview #17660
Conversation
…review/2021-09-03-preview to version 2022-02-02-preview
Hi, @ryanosh 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
|
Rule | Message |
---|---|
Since operation 'MsixImages_Expand' response has model definition 'x-ms-pageable', it should be of the form '_list'. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change. Location: Microsoft.DesktopVirtualization/preview/2022-02-02-preview/desktopvirtualization.json#L2125 |
|
'PUT' operation 'PrivateEndpointConnections_UpdateByHostPool' should use method name 'Create'. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change. Location: Microsoft.DesktopVirtualization/preview/2022-02-02-preview/desktopvirtualization.json#L2606 |
|
'PUT' operation 'PrivateEndpointConnections_UpdateByWorkspace' should use method name 'Create'. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change. Location: Microsoft.DesktopVirtualization/preview/2022-02-02-preview/desktopvirtualization.json#L2841 |
|
Consider using x-ms-client-flatten to provide a better end user experience Location: Microsoft.DesktopVirtualization/preview/2022-02-02-preview/desktopvirtualization.json#L3017 |
|
A PUT operation request body schema should be the same as its 200 response schema, to allow reusing the same entity between GET and PUT. If the schema of the PUT request body is a superset of the GET response body, make sure you have a PATCH operation to make the resource updatable. Operation: 'PrivateEndpointConnections_UpdateByHostPool' Request Model: 'PrivateEndpointConnection' Response Model: 'PrivateEndpointConnectionWithSystemData' Location: Microsoft.DesktopVirtualization/preview/2022-02-02-preview/desktopvirtualization.json#L2602 |
|
A PUT operation request body schema should be the same as its 200 response schema, to allow reusing the same entity between GET and PUT. If the schema of the PUT request body is a superset of the GET response body, make sure you have a PATCH operation to make the resource updatable. Operation: 'PrivateEndpointConnections_UpdateByWorkspace' Request Model: 'PrivateEndpointConnection' Response Model: 'PrivateEndpointConnectionWithSystemData' Location: Microsoft.DesktopVirtualization/preview/2022-02-02-preview/desktopvirtualization.json#L2837 |
|
OperationId should contain the verb: 'expandmsiximage' in:'MsixImages_Expand'. Consider updating the operationId Location: Microsoft.DesktopVirtualization/preview/2022-02-02-preview/desktopvirtualization.json#L2125 |
|
The child tracked resource, 'applications' with immediate parent 'ApplicationGroup', must have a list by immediate parent operation. Location: Microsoft.DesktopVirtualization/preview/2022-02-02-preview/desktopvirtualization.json#L3969 |
|
The child tracked resource, 'desktops' with immediate parent 'ApplicationGroup', must have a list by immediate parent operation. Location: Microsoft.DesktopVirtualization/preview/2022-02-02-preview/desktopvirtualization.json#L4202 |
|
The child tracked resource, 'sessionHosts' with immediate parent 'HostPool', must have a list by immediate parent operation. Location: Microsoft.DesktopVirtualization/preview/2022-02-02-preview/desktopvirtualization.json#L4487 |
|
The child tracked resource, 'msixPackages' with immediate parent 'HostPool', must have a list by immediate parent operation. Location: Microsoft.DesktopVirtualization/preview/2022-02-02-preview/desktopvirtualization.json#L3763 |
|
The child tracked resource, 'userSessions' with immediate parent 'SessionHost', must have a list by immediate parent operation. Location: Microsoft.DesktopVirtualization/preview/2022-02-02-preview/desktopvirtualization.json#L4861 |
|
Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: force Location: Microsoft.DesktopVirtualization/preview/2022-02-02-preview/desktopvirtualization.json#L1431 |
|
Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: force Location: Microsoft.DesktopVirtualization/preview/2022-02-02-preview/desktopvirtualization.json#L1750 |
|
Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: force Location: Microsoft.DesktopVirtualization/preview/2022-02-02-preview/desktopvirtualization.json#L1809 |
|
Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: force Location: Microsoft.DesktopVirtualization/preview/2022-02-02-preview/desktopvirtualization.json#L2252 |
|
Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: isDataAction Location: Microsoft.DesktopVirtualization/preview/2022-02-02-preview/desktopvirtualization.json#L3013 |
|
Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: cloudPcResource Location: Microsoft.DesktopVirtualization/preview/2022-02-02-preview/desktopvirtualization.json#L3107 |
|
Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: cloudPcResource Location: Microsoft.DesktopVirtualization/preview/2022-02-02-preview/desktopvirtualization.json#L3269 |
|
Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: validationEnvironment Location: Microsoft.DesktopVirtualization/preview/2022-02-02-preview/desktopvirtualization.json#L3446 |
|
Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: startVMOnConnect Location: Microsoft.DesktopVirtualization/preview/2022-02-02-preview/desktopvirtualization.json#L3506 |
|
Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: cloudPcResource Location: Microsoft.DesktopVirtualization/preview/2022-02-02-preview/desktopvirtualization.json#L3514 |
|
Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: validationEnvironment Location: Microsoft.DesktopVirtualization/preview/2022-02-02-preview/desktopvirtualization.json#L3608 |
|
Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: startVMOnConnect Location: Microsoft.DesktopVirtualization/preview/2022-02-02-preview/desktopvirtualization.json#L3659 |
|
Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: isRegularRegistration Location: Microsoft.DesktopVirtualization/preview/2022-02-02-preview/desktopvirtualization.json#L3816 |
|
Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: isActive Location: Microsoft.DesktopVirtualization/preview/2022-02-02-preview/desktopvirtualization.json#L3821 |
|
Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: isActive Location: Microsoft.DesktopVirtualization/preview/2022-02-02-preview/desktopvirtualization.json#L3874 |
|
Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: isRegularRegistration Location: Microsoft.DesktopVirtualization/preview/2022-02-02-preview/desktopvirtualization.json#L3878 |
|
Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: showInPortal Location: Microsoft.DesktopVirtualization/preview/2022-02-02-preview/desktopvirtualization.json#L4069 |
|
Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: showInPortal Location: Microsoft.DesktopVirtualization/preview/2022-02-02-preview/desktopvirtualization.json#L4165 |
️️✔️
Avocado succeeded [Detail] [Expand]
Validation passes for Avocado.
️❌
~[Staging] ApiReadinessCheck: 1 Errors, 0 Warnings failed [Detail]
Rule | Message |
---|---|
API Readiness check failed. Please make sure your service is deployed. |
"code: InvalidResourceType, message: The resource type 'operations' could not be found in the namespace 'Microsoft.DesktopVirtualization' for api version '2022-02-02-preview'. The supported api-versions are '2019-01-23-preview, 2019-09-24-preview, 2019-12-10-preview, 2020-09-21-preview, 2020-10-19-preview, 2020-11-02-preview, 2020-11-10-preview, 2021-01-14-preview, 2021-02-01-preview, 2021-03-09-preview, 2021-04-01-preview, 2021-05-13-preview, 2021-08-04-preview, 2021-09-03-preview, 2021-09-17-privatepreview, 2021-07-12'." |
️️✔️
ModelValidation succeeded [Detail] [Expand]
Validation passes for ModelValidation.
️️✔️
SemanticValidation succeeded [Detail] [Expand]
Validation passes for SemanticValidation.
️❌
Cross-Version Breaking Changes: 29 Errors, 61 Warnings failed [Detail]
- Compared Swaggers (Based on Oad v0.9.1)
- current:preview/2022-02-02-preview/desktopvirtualization.json compared with base:stable/2021-07-12/desktopvirtualization.json
- current:preview/2022-02-02-preview/desktopvirtualization.json compared with base:preview/2021-09-03-preview/desktopvirtualization.json
Only 30 items are listed, please refer to log for more details.
️️✔️
CredScan succeeded [Detail] [Expand]
There is no credential detected.
️️✔️
SDK Track2 Validation succeeded [Detail] [Expand]
Validation passes for SDKTrack2Validation
- The following tags are being changed in this PR
️️✔️
PrettierCheck succeeded [Detail] [Expand]
Validation passes for PrettierCheck.
️️✔️
SpellCheck succeeded [Detail] [Expand]
Validation passes for SpellCheck.
️️✔️
Lint(RPaaS) succeeded [Detail] [Expand]
Validation passes for Lint(RPaaS).
Hi, @ryanosh 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
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
Hi, @ryanosh. Your PR has no update for 14 days and it is marked as stale PR. If no further update for over 14 days, the bot will close the PR. If you want to refresh the PR, please remove |
Hi, @ryanosh. The PR will be closed since the PR has no update for 28 days. If you still need the PR review to proceed, please reopen it and @ mention PR assignee. |
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.
-[X] 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.