-
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
fix correctness errors for AVS 2020-03-20 API #11317
Conversation
Azure Pipelines successfully started running 1 pipeline(s). |
azure-sdk-for-net - Release
|
azure-sdk-for-java - 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
|
azure-sdk-for-python - Release
- Breaking Change detected in SDK
|
azure-sdk-for-go - Release
|
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-js - Release
|
azure-resource-manager-schemas - Release
|
Azure Pipelines successfully started running 1 pipeline(s). |
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
|
The 11 errors listed as "breaking changes" fall into two categories:
|
specification/vmware/resource-manager/Microsoft.AVS/stable/2020-03-20/vmware.json
Outdated
Show resolved
Hide resolved
…turn" This reverts commit a2fe16d.
…tials return"" This reverts commit 214ed73.
Azure Pipelines successfully started running 1 pipeline(s). |
Azure Pipelines successfully started running 1 pipeline(s). |
Hi, @ctaggart 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 |
This is considered an urgent issue, so I created an ICM to get this reviewed: |
Hi @ctaggart, 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. |
@ruowan, there is a one single sdk breaking change reported by the pthon sdk check. It is saying:
No other SDK has a breaking change. A stable version of the python SDK has not yet been published, so I do not think this is a blocking issue. If you look at https://pypi.org/project/azure-mgmt-avs/#history, you will see two versions:
The az-vmware-cli uses autorest with --use=@microsoft.azure/autorest.python@3.0.62 and there are no breaking changes. The breaking changes check is using --use=@microsoft.azure/autorest.python@~4.0.71. I'm not sure what version of autorust.python, the 1.0.0rc1 used. I will ask for a stable 1.0.0 of azure-mgmt-avs after this is merged. |
I created this breaking change review: https://msazure.visualstudio.com/One/_workitems/edit/8653604 |
@changlong-liu Could you pls help to review this Python Breaking Change? |
Hi @ruowan @ctaggart , I added comments in the github issue: Azure/azure-sdk-for-python#14735 Hi @ctaggart , |
@changlong-liu those breaking changes are occurring when you run autorest against the current specification: https://github.com/ctaggart/azure-sdk-for-python/pull/1/files#diff-4db79dc989d60426c9b0788a2502c7c7c85acd73e15617a48794ca0691337080R179 There are no breaking changes caused by these spec changes in the Python SDK: ctaggart/azure-sdk-for-python#2 |
@ruowan, the breaking changes review was approved. Please merge this. I'll request new SDK versions after it is merged and KPIs show they are fixed. |
* fix OBJECT_ADDITIONAL_PROPERTIES identified in operation "Operations_List" * remove x-ms-secret from PrivateClouds_ListAdminCredentials return * specify int32 for integers * add provisioningState to ManagementCluster * suppress warnings * prettier * Revert "remove x-ms-secret from PrivateClouds_ListAdminCredentials return" This reverts commit a2fe16d. * try suppressing SECRET_PROPERTY error * Revert "try suppressing SECRET_PROPERTY error" This reverts commit d3a567f. * Revert "Revert "remove x-ms-secret from PrivateClouds_ListAdminCredentials return"" This reverts commit 214ed73. * put back x-ms-secret from PrivateClouds_ListAdminCredentials return This reverts commit 31b80bb. * suppress SECRET_PROPERTY error
This is to fix errors identified in:
https://msazure.visualstudio.com/Swagger%20KPIs/_workitems/edit/8187811
The 11 errors that the CI check lists as "breaking changes" fall into two categories:
These are all for Operations_List, to match what is actually returned.
The lint errors say that a format is required for integer. It was unspecified. They are all int32. I can roll back afa0274 if needed, but I'd prefer to fix this lint error.
The existing SDKs will continue to work against the 2020-03-20 API. The Python SDK reported one breaking change in its API for clusters.create_or_update signature.
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.