-
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
Adding new api version- 2021-03-08 #13524
Conversation
Hi, @renu00 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] |
Thank you for your contribution renu00! We will review the pull request and get back to you soon. |
Swagger Validation Report
|
Rule | Message |
---|---|
'GET' operation 'Workbooks_RevisionsList' should use method name 'Get' or Method name start with 'List'. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change. Location: Microsoft.Insights/stable/2021-03-08/workbooks_API.json#L337 |
|
'GET' operation 'Workbooks_RevisionGet' should use method name 'Get' or Method name start with 'List'. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change. Location: Microsoft.Insights/stable/2021-03-08/workbooks_API.json#L379 |
|
The enum types should have x-ms-enum type extension set with appropriate options. Property name: type Location: Microsoft.Insights/stable/2021-03-08/workbooks_API.json#L697 |
|
Based on the response model schema, operation 'ComponentCurrentBillingFeatures_Get' might be pageable. Consider adding the x-ms-pageable extension. Location: Microsoft.Insights/stable/2015-05-01/componentFeaturesAndPricing_API.json#L38 |
|
Based on the response model schema, operation 'ComponentAvailableFeatures_Get' might be pageable. Consider adding the x-ms-pageable extension. Location: Microsoft.Insights/stable/2015-05-01/componentFeaturesAndPricing_API.json#L177 |
|
'Properties' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. Location: Microsoft.Insights/stable/2015-05-01/analyticsItems_API.json#L269 |
|
'nextLink' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. Location: Microsoft.Insights/stable/2021-03-08/myworkbooks_API.json#L385 |
|
'systemData' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. Location: Microsoft.Insights/stable/2021-03-08/myworkbooks_API.json#L416 |
|
'nextLink' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. Location: Microsoft.Insights/stable/2021-03-08/workbooks_API.json#L484 |
|
'systemData' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. Location: Microsoft.Insights/stable/2021-03-08/workbooks_API.json#L515 |
The following errors/warnings exist before current PR submission:
Rule | Message |
---|---|
R4018 - OperationsApiResponseSchema |
The response schema of operations API '/providers/Microsoft.Insights/operations' does not match the ARM specification. Please standardize the schema. Location: azure-rest-api-specs/blob/d187dd4fc3d8064504d93335efb63e5c706a36b5/undefined#Lundefined |
️️✔️
Avocado succeeded [Detail] [Expand]
Validation passes for Avocado.
️️✔️
ModelValidation succeeded [Detail] [Expand]
Validation passes for ModelValidation.
️️✔️
SemanticValidation succeeded [Detail] [Expand]
Validation passes for SemanticValidation.
️⚠️
[Staging] Cross Version BreakingChange (Base on preview version): 8 Warnings warning [Detail]
- Compared Swaggers (Based on Oad v0.8.8)
- original: preview/2018-06-17-preview/workbookOperations_API.json <---> new: stable/2021-03-08/workbookOperations_API.json
- original: preview/2018-06-17-preview/workbooks_API.json <---> new: stable/2021-03-08/workbooks_API.json
️️✔️
[Staging] Cross Version BreakingChange (Base on stable version) succeeded [Detail] [Expand]
There are no breaking changes.
- Compared Swaggers (Based on Oad v0.8.8)
- original: stable/2020-10-20/myworkbooks_API.json <---> new: stable/2021-03-08/myworkbooks_API.json
- original: stable/2020-10-20/workbookOperations_API.json <---> new: stable/2021-03-08/workbookOperations_API.json
- original: stable/2020-10-20/workbooks_API.json <---> new: stable/2021-03-08/workbooks_API.json
️️✔️
CredScan succeeded [Detail] [Expand]
There is no credential detected.
️❌
[Staging] SDK Track2 Validation: 3 Errors, 0 Warnings failed [Detail]
- The following tags are being changed in this PR
Rule | Message |
---|---|
PreCheck/DuplicateSchema |
"readme":"applicationinsights/resource-manager/readme.md", "tag":"package-2021-03-08", "details":"Duplicate Schema named ManagedIdentity -- properties.userAssignedIdentities.$ref: undefined => "#/components/schemas/schemas:350" ; This error can be temporarily avoided by using the 'modelerfour.lenient-model-deduplication' setting. NOTE: This setting will be removed in a future version of @autorest/modelerfour; schemas should be updated to fix this issue sooner than that." |
PreCheck/DuplicateSchema |
"readme":"applicationinsights/resource-manager/readme.md", "tag":"package-2021-03-08", "details":"Duplicate Schema named UserAssignedIdentities -- properties.clientId: undefined => "description":"The client ID of resource.", "readOnly":true, "$ref":"#/components/schemas/schemas:353" ; This error can be temporarily avoided by using the 'modelerfour.lenient-model-deduplication' setting. NOTE: This setting will be removed in a future version of @autorest/modelerfour; schemas should be updated to fix this issue sooner than that." |
AutorestCore/Exception |
"readme":"applicationinsights/resource-manager/readme.md", "tag":"package-2021-03-08", "details":"Error: Plugin prechecker reported failure." |
️️✔️
[Staging] PrettierCheck succeeded [Detail] [Expand]
Validation passes for PrettierCheck.
️️✔️
[Staging] SpellCheck succeeded [Detail] [Expand]
Validation passes for SpellCheck.
Swagger Generation Artifacts
|
Hi @renu00, Your PR has some issues. Please fix the CI sequentially by following the order of
|
…api-versions to 2021-03-08
NewApiVersionRequired reason: |
Hey @lmazuel , Can you please review this PR? |
…g their api-versions to 2021-03-08" This reverts commit 8abd9f1.
Hi, @renu00 your PR are labelled with WaitForARMFeedback. A notification email will be sent out shortly afterwards to notify ARM review board([email protected]). cc @lmazuel |
@akning-ms @lmazuel Since we are blocked on the ARM review, I went to go create an IcM as its written in the step above. however, it looks like the suggested Team "RP Manifest Approvers" doesn't exist under "Azure Resource Manager" service. |
Hi @tonykslee, you don't need to create IcM ticket for ARM team. you can ping on-call person to help you review the PR. |
I've reposted this PR here to include a first commit with unmodified existing files #14041 |
MSFT employees can try out our new experience at OpenAPI Hub - one location for using our validation tools and finding your workflow.
Changelog
Please ensure to add changelog with 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
Ensure to check this box if one of the following scenarios meet updates in the PR, so that label “WaitForARMFeedback” will be added automatically to involve ARM API Review. Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs, all “removals” and “adding a new property” no more require ARM API review.
Please 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 there are following updates in the PR, ensure to request an approval from 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.