[ADLA] - Adding existing Catalog ACL APIs#1952
Conversation
* This is to follow the guidelines about having multiple paths with the same definition but with different query parameters
* This is not supported
|
Hi There, I am the AutoRest Linter Azure bot. I am here to help. My task is to analyze the situation from the AutoRest linter perspective. Please review the below analysis result: File: AutoRest Linter Guidelines | AutoRest Linter Issues | Send feedback Thanks for your co-operation. |
| "$ref": "#/definitions/AclList" | ||
| } | ||
| }, | ||
| "404": { |
There was a problem hiding this comment.
All the negative response status code descriptions MUST be defined in the description of the "default" status code (if the intention is for documentation purpose only). Example: "description": "'404' - 'Not found'.\n'400' - 'Bad request'.\n'500': 'Internal Server Error'."'
There was a problem hiding this comment.
Thanks, @jianghaolu! Fixed it, but let me know if I need to add the single quotes.
|
Hi There, I am the AutoRest Linter Azure bot. I am here to help. My task is to analyze the situation from the AutoRest linter perspective. Please review the below analysis result: File: AutoRest Linter Guidelines | AutoRest Linter Issues | Send feedback Thanks for your co-operation. |
|
No modification for AutorestCI/azure-sdk-for-ruby |
|
No modification for AutorestCI/azure-sdk-for-node |
* Optional serviceName property in namespace properties * New API version to introduce optional parameter * Fix Swagger error * Fix Swagger error * Fix ListFalconOperations.json * Fix readme.md * Add default response to Patch operation * Add openapi-subtype * Update readme files
Adding six existing ACL APIs for Catalog -- thus this PR is to fill in the missing gap.
Since they were existing, we could not give feedback about the usage of OP to define the call. We will work on possibly removing this and redesigning it in a new API version for Catalog, which is in progress.
This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.
PR information
api-versionin the path should match theapi-versionin the spec).Quality of Swagger