AzureDataShare: Adding version 2020-10-01-preview swagger #12878
AzureDataShare: Adding version 2020-10-01-preview swagger #12878akning-ms merged 7 commits intoAzure:masterfrom ahermas:ahermas/V5_2020-10-01-preview_swagger
Conversation
|
Hi, @ahermas 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 |
Swagger Validation Report
|
| Rule | Message |
|---|---|
| Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: fillGapWithZero Location: Microsoft.DataShare/preview/2020-10-01-preview/DataShare.json#L5135 |
️️✔️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): 9 Warnings warning [Detail]
- Compared Swaggers (Based on Oad v0.8.6)
- original: preview/2018-11-01-preview/DataShare.json <---> new: preview/2020-10-01-preview/DataShare.json
| Rule | Message |
|---|---|
| The new version is missing a path that was found in the old version. Was path '/providers/Microsoft.DataShare/ListInvitations' removed or restructured? Old: Microsoft.DataShare/preview/2018-11-01-preview/DataShare.json#L314:5 |
|
| The new version is missing a path that was found in the old version. Was path '/providers/Microsoft.DataShare/locations/{location}/RejectInvitation' removed or restructured? Old: Microsoft.DataShare/preview/2018-11-01-preview/DataShare.json#L406:5 |
|
| The new version is missing a path that was found in the old version. Was path '/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DataShare/accounts/{accountName}/shareSubscriptions/{shareSubscriptionName}/ConsumerSourceDataSets' removed or restructured? Old: Microsoft.DataShare/preview/2018-11-01-preview/DataShare.json#L1988:5 |
|
| The new version is missing a path that was found in the old version. Was path '/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DataShare/accounts/{accountName}/shareSubscriptions/{shareSubscriptionName}/Synchronize' removed or restructured? Old: Microsoft.DataShare/preview/2018-11-01-preview/DataShare.json#L2265:5 |
|
| The required parameter 'providerShareSubscription' was added in the new version. New: Microsoft.DataShare/preview/2020-10-01-preview/DataShare.json#L1556:11 |
|
| The new version has a different 'allOf' property than the previous one. New: Microsoft.DataShare/preview/2020-10-01-preview/DataShare.json#L4637:5 Old: Microsoft.DataShare/preview/2018-11-01-preview/DataShare.json#L4538:5 |
|
| The new version has new required property 'sourceShareLocation' that was not found in the old version. New: Microsoft.DataShare/preview/2020-10-01-preview/DataShare.json#L5782:7 Old: Microsoft.DataShare/preview/2018-11-01-preview/DataShare.json#L5674:7 |
|
| The new version has new required property 'sourceShareLocation' that was not found in the old version. New: Microsoft.DataShare/preview/2020-10-01-preview/DataShare.json#L5747:9 Old: Microsoft.DataShare/preview/2018-11-01-preview/DataShare.json#L5640:9 |
|
| The new version has new required property 'sourceShareLocation' that was not found in the old version. New: Microsoft.DataShare/preview/2020-10-01-preview/DataShare.json#L5775:5 Old: Microsoft.DataShare/preview/2018-11-01-preview/DataShare.json#L5668:5 |
️️✔️[Staging] Cross Version BreakingChange (Base on stable version) succeeded [Detail] [Expand]
There are no breaking changes.
- Compared Swaggers (Based on Oad v0.8.6)
- original: stable/2020-09-01/DataShare.json <---> new: preview/2020-10-01-preview/DataShare.json
️️✔️CredScan succeeded [Detail] [Expand]
There is no credential detected.
️⚠️[Staging] SDK Track2 Validation: 1 Warnings warning [Detail]
- The following tags are being changed in this PR
| Rule | Message |
|---|---|
| "readme":"datashare/resource-manager/readme.md", "tag":"package-2020-10-01-preview", "details":"Checking for duplicate schemas, this could take a (long) while. Run with --verbose for more detail." |
️️✔️[Staging] PrettierCheck succeeded [Detail] [Expand]
Validation passes for PrettierCheck.
️️✔️[Staging] SpellCheck succeeded [Detail] [Expand]
Validation passes for SpellCheck.
Swagger Generation Artifacts
|
|
Hi @ahermas, Your PR has some issues. Please fix the CI sequentially by following the order of
|
… update readme files
|
Hi, @ahermas your PR are labelled with WaitForARMFeedback. A notification email will be sent out shortly afterwards to notify ARM review board(armapireview@microsoft.com). cc @ChenTanyi |
|
@ChenTanyi I see that the PR has cli errors. I pinged the autorest team but I was wondering if you know about such errors and how they could be resolved. Thanks. |
|
/azp run |
|
Azure Pipelines successfully started running 2 pipeline(s). |
|
@ahermas The Cli CI has passed |
is this a bug fix where the schema now reflects what the service supports? or is this an intentional functionality degradation from the previous api version? Refers to: specification/datashare/resource-manager/Microsoft.DataShare/preview/2020-10-01-preview/DataShare.json:4710 in 0df549e. [](commit_id = 0df549e, deletion_comment = False) |
consider modeling the containerName, location and storageAccountResourceId within a "storageAccount" object with those 3 fields Refers to: specification/datashare/resource-manager/Microsoft.DataShare/preview/2020-10-01-preview/DataShare.json:6431 in 0df549e. [](commit_id = 0df549e, deletion_comment = False) |
@varunkumta UserAssigned was added by mistake. My change is to remove it. |
...oft.DataShare/preview/2020-10-01-preview/examples/DataSetMappings_StorageAccount_Create.json
Outdated
Show resolved
Hide resolved
@varunkumta location is a read only property exposed to the customer. We would like to keep it a separate entry in the property bag. |
@varunkumta StorageAccountDataSetProperties already contains what you're referring to as a "storageaccount". |
|
@varunkumta @ChenTanyi @ArcturusZhang |
|
@ahermas please let me know when it ready to merge. |
@ChenTanyi we found a minor issue and we are working on fixing it. Please hold merging this. |
@ChenTanyi The minor issue has been addressed.Please merge the PR when you get a chance. |
|
Hi @ArcturusZhang, I'm pinging you since I see the Chen will be away till the 17th. Thanks |
|
/azp run |
|
Azure Pipelines successfully started running 2 pipeline(s). |
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.