-
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
[LogicApp] Bugfix for swagger/sdk not matching the underlying service API #4769
[LogicApp] Bugfix for swagger/sdk not matching the underlying service API #4769
Conversation
If you're a MSFT employee, click this link |
Automation for azure-sdk-for-pythonThe initial PR has been merged into your service PR: |
Automation for azure-sdk-for-jsThe initial PR has been merged into your service PR: |
Automation for azure-sdk-for-rubyThe initial PR has been merged into your service PR: |
Automation for azure-sdk-for-goThe initial PR has been merged into your service PR: |
Can one of the admins verify this patch? |
Automation for azure-sdk-for-nodeThe initial PR has been merged into your service PR: |
Automation for azure-sdk-for-javaThe initial PR has been merged into your service PR: |
@refortie This needs exception approval from ARM Team. Please contact Gaurav Bhatnagar to get the exception approval |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As a bugfix to align to existing service behavior, this is OK from ARM
@refortie Since ARM has approved the changes could you please add the exception to the Readme file so the CI will pass. You can use this as reference: https://github.com/Azure/azure-rest-api-specs/tree/master/specification/apimanagement/resource-manager#suppression-1 |
… API (Azure#4769) * Bugfix for swagger/sdk not matching the underlying service API * Add in approved override
I understand this breaks the naming convention specified, but this is a bugfix not a new feature. Our API returns these 2 acronyms as capitalized words. This causes any case sensitive JSON deserialization in the the SDKs to not be able to deserialize the responses from the API An example of this is calling the GET call in the node SDK.
Latest improvements:
MSFT employees can try out our new experience at OpenAPI Hub - one location for using our validation tools and finding your workflow.
Contribution checklist:
ARM API Review Checklist
Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.
Please follow the link to find more details on API review process.