-
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
[Hub Generated] Review request for Microsoft.DigitalTwins to add version stable/2020-12-01 #10996
[Hub Generated] Review request for Microsoft.DigitalTwins to add version stable/2020-12-01 #10996
Conversation
…0-10-31 to version 2020-12-01
Swagger Validation Report
|
Rule | Message |
---|---|
Consider using x-ms-client-flatten to provide a better end user experience New: Microsoft.DigitalTwins/stable/2020-12-01/digitaltwins.json#L1729 |
|
Consider using x-ms-client-flatten to provide a better end user experience New: Microsoft.DigitalTwins/stable/2020-12-01/digitaltwins.json#L1564 |
|
Consider using x-ms-client-flatten to provide a better end user experience New: Microsoft.DigitalTwins/stable/2020-12-01/digitaltwins.json#L1040 |
|
Based on the response model schema, operation 'PrivateEndpointConnections_List' might be pageable. Consider adding the x-ms-pageable extension. New: Microsoft.DigitalTwins/stable/2020-12-01/digitaltwins.json#L729 |
|
Based on the response model schema, operation 'PrivateLinkResources_List' might be pageable. Consider adding the x-ms-pageable extension. New: Microsoft.DigitalTwins/stable/2020-12-01/digitaltwins.json#L642 |
|
'privateEndpointConnections' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. New: Microsoft.DigitalTwins/stable/2020-12-01/digitaltwins.json#L986 |
|
'properties' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. New: Microsoft.DigitalTwins/stable/2020-12-01/digitaltwins.json#L1564 |
|
'privateEndpoint' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. New: Microsoft.DigitalTwins/stable/2020-12-01/digitaltwins.json#L1685 |
|
'privateLinkServiceConnectionState' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. New: Microsoft.DigitalTwins/stable/2020-12-01/digitaltwins.json#L1699 |
|
'properties' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. New: Microsoft.DigitalTwins/stable/2020-12-01/digitaltwins.json#L1729 |
️️✔️
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): 75 Warnings warning [Detail]
Only 10 items are listed, please refer to log for more details.
- Compared Swaggers (Based on Oad v0.8.1)
- original: preview/2020-03-01-preview/digitaltwins.json <---> new: stable/2020-12-01/digitaltwins.json
️⚠️
[Staging] Cross Version BreakingChange (Base on stable version): 19 Warnings warning [Detail]
Only 10 items are listed, please refer to log for more details.
- Compared Swaggers (Based on Oad v0.8.1)
- original: stable/2020-10-31/digitaltwins.json <---> new: stable/2020-12-01/digitaltwins.json
️️✔️
CredScan succeeded [Detail] [Expand]
There is no credential detected.
Azure Pipelines successfully started running 1 pipeline(s). |
Azure CLI Extension Generation
No readme.md specification configuration files were found that are associated with the files modified in this pull request, or swagger_to_sdk section in readme.md is not configured
|
azure-sdk-for-go
|
azure-sdk-for-js
|
azure-sdk-for-java
|
azure-sdk-for-net
No readme.md specification configuration files were found that are associated with the files modified in this pull request, or swagger_to_sdk section in readme.md is not configured
|
azure-sdk-for-python
|
azure-sdk-for-python-track2
No readme.md specification configuration files were found that are associated with the files modified in this pull request, or swagger_to_sdk section in readme.md is not configured
|
azure-resource-manager-schemas
|
Trenton Generation
No readme.md specification configuration files were found that are associated with the files modified in this pull request, or swagger_to_sdk section in readme.md is not configured
|
@ChenTanyi , @erich-wang : since ARM has now signed off on the PR, please merge this PR as soon as possible. We are planning on opening this version up to the public within the next 2 weeks. |
/azp run |
Azure Pipelines successfully started running 2 pipeline(s). |
@sjiherzig Please fix the LintDiff error. |
@ChenTanyi There is a known problem in codegen tool, so please ignore the failure temporarily. |
@ChenTanyi - this is a new error, and I think it used to be a warning. We are not planning to support systemData in this API version (OK per ARM, as seen in review comments), but only in the next version. |
@jianyexi @akning-ms What's your opinion? @sjiherzig Due to the CI is required, I cannot merge when CI error. If so, it needs @akning-ms for helping force merge. |
/azp run |
Azure Pipelines successfully started running 2 pipeline(s). |
Hi, @sjiherzig 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] |
@ChenTanyi - per @jianyexi's e-mail, we've gone through the swagger suppression process. ARM has signed off on the change. Linter check now passes. Since the Python SDK still fails (known), can you please have @akning-ms force merge? |
@akning-ms please help to merge it. |
…ion stable/2020-12-01 (Azure#10996) * Adds base for updating Microsoft.DigitalTwins from version stable/2020-10-31 to version 2020-12-01 * Updates readme * Updates API version in new specs and examples * Update swagger spec * Modify SDK build configs * Fix example filename reference * Rename example file * Fix validation errors * Updated examples * Revert change to behavior of async op * Modify discriminators * Enable two discriminators * Fix delete endpoint example * Attempted fix with discriminator * Added westus2, change discriminator enum type name * Decouple allOf from properties * Bugfixes * Modify response to fix validation errors * Fix examples * Change private link type names to be smaller * Fix validation errors in private links * Fix validation error related to private links * Reference private link example * Add public network access * Align with GA swagger * Update private links / private endpoints * Fix example to use actual response status code * Remove unused example * Unmark private endpoint connection to be an azure resource * Add type and name to private endpoint connection resource * Mark id as read-only * Fix return types for endpoint connections * Align return of DELETE * Fix validation errors * Fix version tag in python.md; remove body from DELETE endpoint connection DELETE responses * Synchronize swagger with 2020-10-31 version * Increase resource group name max length to 90 characters * Make publicNetworkAccess nullable * Add publicNetworkAccess flag to PATCH request * Fixed typo * Fix placing of example for endpoints * Update operation ids * Added suppression message
…ion stable/2020-12-01 (Azure#10996) * Adds base for updating Microsoft.DigitalTwins from version stable/2020-10-31 to version 2020-12-01 * Updates readme * Updates API version in new specs and examples * Update swagger spec * Modify SDK build configs * Fix example filename reference * Rename example file * Fix validation errors * Updated examples * Revert change to behavior of async op * Modify discriminators * Enable two discriminators * Fix delete endpoint example * Attempted fix with discriminator * Added westus2, change discriminator enum type name * Decouple allOf from properties * Bugfixes * Modify response to fix validation errors * Fix examples * Change private link type names to be smaller * Fix validation errors in private links * Fix validation error related to private links * Reference private link example * Add public network access * Align with GA swagger * Update private links / private endpoints * Fix example to use actual response status code * Remove unused example * Unmark private endpoint connection to be an azure resource * Add type and name to private endpoint connection resource * Mark id as read-only * Fix return types for endpoint connections * Align return of DELETE * Fix validation errors * Fix version tag in python.md; remove body from DELETE endpoint connection DELETE responses * Synchronize swagger with 2020-10-31 version * Increase resource group name max length to 90 characters * Make publicNetworkAccess nullable * Add publicNetworkAccess flag to PATCH request * Fixed typo * Fix placing of example for endpoints * Update operation ids * Added suppression message
This is a PR generated at OpenAPI Hub. You can view your work branch via this link.
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.
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 API Review Board as defined in the Breaking Change Policy.
Please follow the link to find more details on PR review process.