-
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
TestBase 2022-04-01-preview (from RPaaSMaster) #19419
TestBase 2022-04-01-preview (from RPaaSMaster) #19419
Conversation
Hi, @jujiang-msft 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, @jujiang-msft 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
|
Rule | Message |
---|---|
Since operation 'BillingHubService_GetFreeHourBalance' 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.TestBase/preview/2022-04-01-preview/testbase.json#L2509 |
|
The operation 'Packages_RunTest' returns 202 status code, which indicates a long running operation, please enable 'x-ms-long-running-operation. Location: Microsoft.TestBase/preview/2022-04-01-preview/testbase.json#L1313 |
|
'getUsageRequest' parameter lacks 'description' property. Consider adding a 'description' element. Accurate description is essential for maintaining reference documentation. Location: Microsoft.TestBase/preview/2022-04-01-preview/testbase.json#L2578 |
|
'BillingHubExecutionUsageDetail' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. Location: Microsoft.TestBase/preview/2022-04-01-preview/testbase.json#L4904 |
|
'applicationName' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. Location: Microsoft.TestBase/preview/2022-04-01-preview/testbase.json#L4907 |
|
'applicationVersion' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. Location: Microsoft.TestBase/preview/2022-04-01-preview/testbase.json#L4910 |
|
'executionRequestId' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. Location: Microsoft.TestBase/preview/2022-04-01-preview/testbase.json#L4913 |
|
'sku' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. Location: Microsoft.TestBase/preview/2022-04-01-preview/testbase.json#L4916 |
|
'meterId' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. Location: Microsoft.TestBase/preview/2022-04-01-preview/testbase.json#L4919 |
|
'startTimeStamp' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. Location: Microsoft.TestBase/preview/2022-04-01-preview/testbase.json#L4922 |
|
'endTimeStamp' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. Location: Microsoft.TestBase/preview/2022-04-01-preview/testbase.json#L4926 |
|
'osBuild' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. Location: Microsoft.TestBase/preview/2022-04-01-preview/testbase.json#L4930 |
|
'release' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. Location: Microsoft.TestBase/preview/2022-04-01-preview/testbase.json#L4933 |
|
'testType' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. Location: Microsoft.TestBase/preview/2022-04-01-preview/testbase.json#L4936 |
|
'updateType' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. Location: Microsoft.TestBase/preview/2022-04-01-preview/testbase.json#L4939 |
|
'usedFreeHours' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. Location: Microsoft.TestBase/preview/2022-04-01-preview/testbase.json#L4942 |
|
'usedBillableHours' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. Location: Microsoft.TestBase/preview/2022-04-01-preview/testbase.json#L4946 |
|
'billedCharges' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. Location: Microsoft.TestBase/preview/2022-04-01-preview/testbase.json#L4950 |
|
'BillingHubGetFreeHourBalanceResponse' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. Location: Microsoft.TestBase/preview/2022-04-01-preview/testbase.json#L4956 |
|
'totalRemainingFreeHours' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. Location: Microsoft.TestBase/preview/2022-04-01-preview/testbase.json#L4959 |
|
'incrementEntries' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. Location: Microsoft.TestBase/preview/2022-04-01-preview/testbase.json#L4963 |
|
'BillingHubFreeHourIncrementEntry' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. Location: Microsoft.TestBase/preview/2022-04-01-preview/testbase.json#L4972 |
|
'createTimeStamp' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. Location: Microsoft.TestBase/preview/2022-04-01-preview/testbase.json#L4975 |
|
'expirationTimeStamp' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. Location: Microsoft.TestBase/preview/2022-04-01-preview/testbase.json#L4979 |
|
'incrementalFreeHours' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. Location: Microsoft.TestBase/preview/2022-04-01-preview/testbase.json#L4983 |
|
'remainingFreeHours' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. Location: Microsoft.TestBase/preview/2022-04-01-preview/testbase.json#L4987 |
|
'BillingHubGetUsageResponse' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. Location: Microsoft.TestBase/preview/2022-04-01-preview/testbase.json#L4993 |
|
'totalUsedFreeHours' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. Location: Microsoft.TestBase/preview/2022-04-01-preview/testbase.json#L4996 |
|
'totalUsedBillableHours' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. Location: Microsoft.TestBase/preview/2022-04-01-preview/testbase.json#L5000 |
|
'totalCharges' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. Location: Microsoft.TestBase/preview/2022-04-01-preview/testbase.json#L5004 |
The following errors/warnings exist before current PR submission:
Only 30 items are listed, please refer to log for more details.
️️✔️
Avocado succeeded [Detail] [Expand]
Validation passes for Avocado.
️️✔️
ApiReadinessCheck succeeded [Detail] [Expand]
️️✔️
ModelValidation succeeded [Detail] [Expand]
Validation passes for ModelValidation.
️️✔️
SemanticValidation succeeded [Detail] [Expand]
Validation passes for SemanticValidation.
️⚠️
Cross-Version Breaking Changes: 240 Warnings warning [Detail]
- Compared Swaggers (Based on Oad v0.9.5)
- current:preview/2022-04-01-preview/testbase.json compared with base:preview/2020-12-16-preview/testbase.json
Only 30 items are listed, please refer to log for more details.
️️✔️
CredScan succeeded [Detail] [Expand]
There is no credential detected.
️️✔️
PoliCheck succeeded [Detail] [Expand]
Validation passed for PoliCheck.
️️✔️
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
|
API has been reviewed and approved by ARM team in private repo PR https://github.com/Azure/azure-rest-api-specs-pr/pull/6630 |
@leni-msft can you please help merge? |
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.