-
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
Gargankit/azure cli test #18100
Gargankit/azure cli test #18100
Conversation
Hi, @gargankit-microsoft 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. |
Swagger Validation Report
|
Rule | Message |
---|---|
Since operation 'SAPSupportedSku' response has model definition 'array', 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.Workloads/preview/2021-12-01-preview/SAPVirtualInstance.json#L99 |
|
Since operation 'SAPDiskConfigurations' response has model definition 'array', 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.Workloads/preview/2021-12-01-preview/SAPVirtualInstance.json#L155 |
|
Since operation 'SAPAvailabilityZoneDetails' response has model definition 'array', 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.Workloads/preview/2021-12-01-preview/SAPVirtualInstance.json#L205 |
|
Consider using x-ms-client-flatten to provide a better end user experience Location: Microsoft.Workloads/preview/2021-12-01-preview/SAPVirtualInstance.json#L1699 |
|
OperationId should contain the verb: 'getsizingrecommendations' in:'SAPSizingRecommendations'. Consider updating the operationId Location: Microsoft.Workloads/preview/2021-12-01-preview/SAPVirtualInstance.json#L43 |
|
OperationId should contain the verb: 'getsapsupportedsku' in:'SAPSupportedSku'. Consider updating the operationId Location: Microsoft.Workloads/preview/2021-12-01-preview/SAPVirtualInstance.json#L99 |
|
OperationId should contain the verb: 'getdiskconfigurations' in:'SAPDiskConfigurations'. Consider updating the operationId Location: Microsoft.Workloads/preview/2021-12-01-preview/SAPVirtualInstance.json#L155 |
|
OperationId should contain the verb: 'getavailabilityzonedetails' in:'SAPAvailabilityZoneDetails'. Consider updating the operationId Location: Microsoft.Workloads/preview/2021-12-01-preview/SAPVirtualInstance.json#L205 |
|
The child tracked resource, 'applicationInstances' with immediate parent 'SAPVirtualInstance', must have a list by immediate parent operation. Location: Microsoft.Workloads/preview/2021-12-01-preview/SAPVirtualInstance.json#L2859 |
|
The child tracked resource, 'centralInstances' with immediate parent 'SAPVirtualInstance', must have a list by immediate parent operation. Location: Microsoft.Workloads/preview/2021-12-01-preview/SAPVirtualInstance.json#L3033 |
|
The child tracked resource, 'databaseInstances' with immediate parent 'SAPVirtualInstance', must have a list by immediate parent operation. Location: Microsoft.Workloads/preview/2021-12-01-preview/SAPVirtualInstance.json#L3100 |
|
Guid used in model definition 'UserAssignedIdentity' for property 'principalId'. Usage of Guid is not recommanded. If GUIDs are absolutely required in your service, please get sign off from the Azure API review board. Location: Microsoft.Workloads/preview/2021-12-01-preview/managedidentity.json#L21 |
|
Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: disablePasswordAuthentication Location: Microsoft.Workloads/preview/2021-12-01-preview/SAPVirtualInstance.json#L1841 |
|
Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: isAppServerCertified Location: Microsoft.Workloads/preview/2021-12-01-preview/SAPVirtualInstance.json#L2059 |
|
Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: isDatabaseCertified Location: Microsoft.Workloads/preview/2021-12-01-preview/SAPVirtualInstance.json#L2063 |
|
Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: hardStop Location: Microsoft.Workloads/preview/2021-12-01-preview/SAPVirtualInstance.json#L2510 |
|
Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: isDataAction Location: Microsoft.Workloads/preview/2021-12-01-preview/types.json#L373 |
|
'identity' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. Location: Microsoft.Workloads/preview/2021-12-01-preview/SAPVirtualInstance.json#L1718 |
|
'virtualMachineId' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. Location: Microsoft.Workloads/preview/2021-12-01-preview/SAPVirtualInstance.json#L2592 |
|
'virtualMachineId' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. Location: Microsoft.Workloads/preview/2021-12-01-preview/SAPVirtualInstance.json#L2602 |
|
'identity' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. Location: Microsoft.Workloads/preview/2021-12-01-preview/SAPVirtualInstance.json#L2688 |
️❌
Avocado: 2 Errors, 0 Warnings failed [Detail]
Rule | Message |
---|---|
INCONSISTENT_API_VERSION |
The API version of the swagger is inconsistent with its file path. readme: specification/workloads/resource-manager/readme.md json: Microsoft.Workloads/preview/2021-12-01-preview/types.json |
INCONSISTENT_API_VERSION |
The API version of the swagger is inconsistent with its file path. readme: specification/workloads/resource-manager/readme.md json: Microsoft.Workloads/preview/2021-12-01-preview/managedidentity.json |
️️✔️
~[Staging] ApiReadinessCheck succeeded [Detail] [Expand]
️️✔️
ModelValidation succeeded [Detail] [Expand]
Validation passes for ModelValidation.
️️✔️
SemanticValidation succeeded [Detail] [Expand]
Validation passes for SemanticValidation.
️️✔️
Cross-Version Breaking Changes succeeded [Detail] [Expand]
There are no breaking changes.
️️✔️
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).
Swagger Generation Artifacts
|
Hi @gargankit-microsoft, Your PR has some issues. Please fix the CI sequentially by following the order of
|
…wed: x-ms-identifiers" This reverts commit 8ff859f.
Hi, @gargankit-microsoft your PR are labelled with WaitForARMFeedback. A notification email will be sent out shortly afterwards to notify ARM review board(armapireview@microsoft.com). |
Hi, @gargankit-microsoft. 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, @gargankit-microsoft. 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. |
Hi, @gargankit-microsoft. The PR has be closed for a long time and it's related branch still exist. Please tell me if you still need this branch or i will delete it in 14 days. |
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.