Updated HybridNetwork Swaggers for October release.#11232
Updated HybridNetwork Swaggers for October release.#11232raych1 merged 1 commit intoAzure:masterfrom congl-microsoft:HybridNetwork/OctRelease
Conversation
[Staging] Swagger Validation Report
Only 10 items are listed, please refer to log for more details.
❌ |
| Rule | Message |
|---|---|
1005 - RemovedPath |
The new version is missing a path that was found in the old version. Was path '/subscriptions/{subscriptionId}/providers/Microsoft.HybridNetwork/locations/{locationName}/vendors/{vendorName}/virtualNetworkFunctions' removed or restructured? Old: Microsoft.HybridNetwork/preview/2020-01-01-preview/vendor.json#L575:5 |
1005 - RemovedPath |
The new version is missing a path that was found in the old version. Was path '/subscriptions/{subscriptionId}/providers/Microsoft.HybridNetwork/locations/{locationName}/vendors/{vendorName}/virtualNetworkFunctions/{serviceKey}' removed or restructured? Old: Microsoft.HybridNetwork/preview/2020-01-01-preview/vendor.json#L444:5 |
1006 - RemovedDefinition |
The new version is missing a definition that was found in the old version. Was 'VendorProvisioningState' removed or renamed? New: Microsoft.HybridNetwork/preview/2020-01-01-preview/vendor.json#L691:3 Old: Microsoft.HybridNetwork/preview/2020-01-01-preview/vendor.json#L882:3 |
1006 - RemovedDefinition |
The new version is missing a definition that was found in the old version. Was 'VendorVirtualNetworkFunction' removed or renamed? New: Microsoft.HybridNetwork/preview/2020-01-01-preview/vendor.json#L691:3 Old: Microsoft.HybridNetwork/preview/2020-01-01-preview/vendor.json#L882:3 |
1006 - RemovedDefinition |
The new version is missing a definition that was found in the old version. Was 'VirtualNetworkFunctionTemplate' removed or renamed? New: Microsoft.HybridNetwork/preview/2020-01-01-preview/vendor.json#L691:3 Old: Microsoft.HybridNetwork/preview/2020-01-01-preview/vendor.json#L882:3 |
1006 - RemovedDefinition |
The new version is missing a definition that was found in the old version. Was 'VendorVirtualNetworkFunctionPropertiesFormat' removed or renamed? New: Microsoft.HybridNetwork/preview/2020-01-01-preview/vendor.json#L691:3 Old: Microsoft.HybridNetwork/preview/2020-01-01-preview/vendor.json#L882:3 |
1007 - RemovedClientParameter |
The new version is missing a client parameter that was found in the old version. Was 'ApiVersionParameter' removed or renamed? Old: Microsoft.HybridNetwork/preview/2020-01-01-preview/common.json#L262:3 |
1007 - RemovedClientParameter |
The new version is missing a client parameter that was found in the old version. Was 'SubscriptionIdParameter' removed or renamed? Old: Microsoft.HybridNetwork/preview/2020-01-01-preview/common.json#L262:3 |
1020 - AddedEnumValue |
The new version is adding enum value(s) 'Deleted' from the old version. New: Microsoft.HybridNetwork/preview/2020-01-01-preview/device.json#L401:9 Old: Microsoft.HybridNetwork/preview/2020-01-01-preview/device.json#L425:9 |
1020 - AddedEnumValue |
The new version is adding enum value(s) 'Firewall' from the old version. New: Microsoft.HybridNetwork/preview/2020-01-01-preview/vendor.json#L748:9 Old: Microsoft.HybridNetwork/preview/2020-01-01-preview/vendor.json#L939:9 |
️️✔️LintDiff [Detail]
️✔️Validation passes for LintDiff.
️️✔️Avocado [Detail]
️✔️Validation passes for Avocado.
️️✔️ModelValidation [Detail]
️✔️Validation passes for ModelValidation.
️️✔️SemanticValidation [Detail]
️✔️Validation passes for SemanticValidation.
|
Azure Pipelines successfully started running 1 pipeline(s). |
Azure CLI Extension Generation - Release
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 - Release
|
azure-sdk-for-net - Release
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 - Release
|
azure-sdk-for-python-track2 - Release
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
|
|
Hi @raych1 , since there are lots of breaking changes that complained by the pipeline, please refer to our last PR to RPSaaSMaster (https://github.com/Azure/azure-rest-api-specs-pr/pull/2142). Thanks! |
azure-resource-manager-schemas - Release
|
Trenton Generation - Release
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
|
|
Hi @congl-microsoft, one or multiple breaking change(s) is detected in your PR. Pls follow breaking change policy to request breaking change review and approval before proceeding swagger PR review. |
|
@congl-microsoft , could you clarify the changes? From the title that says "October release", however it updated the current preview swagger(2020-01-01-preview). As identified in the check, this PR has breaking changes that needs review from breaking change review board. |
|
Hi @raych1 , thank you very much for asking. Yes, this PR contains lots of breaking changes because the current Swaggers on Master is out-dated. It has been a long time that our team didn't update Swaggers to Master branch because our service was still under private preview. We didn't publish any SDK as well. So using the same version with breaking changes will not impact any customers. For the past months, we changed Swaggers a lot on RPSaaSMaster, and each time we followed the reviewers' feedback and got the changes approved. For now, this PR is exactly the same content as our current Swaggers on RPSaaSMaster which was updated a few days ago and merged by Allen Zhang. Before that PR, there was also a PR merged in August. I just share the two PR links here for your reference. [https://github.com/Azure/azure-rest-api-specs-pr/pull/1898] [https://github.com/Azure/azure-rest-api-specs-pr/pull/2142] Would you please let us know if we need to go through the same review process as we already had on RPSaaSMaster? Please feel free to reach out to me on Teams (congl) if you have any concerns. |
Breaking change approved as this is preview swagger with no published SDK. |
MSFT employees can try out our new experience at OpenAPI Hub - one location for using our validation tools and finding your workflow.
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 API Review Board as defined in the Breaking Change Policy.
Please follow the link to find more details on PR review process.