[Azure Analysis Services] Add gateway info to version 0714 and version 0801#1526
[Azure Analysis Services] Add gateway info to version 0714 and version 0801#1526olydis merged 11 commits intoAzure:currentfrom
Conversation
|
@taiwu, The agreement will cover your contributions to all Microsoft-managed open source projects. |
|
Sync and add older version as requested in |
|
@taiwu Please complete the checklist. Regarding vendor message: Seems like the PR was still tagged as "cla-not-required", so you can ignore that. (classification is flaky sometimes) |
|
@olydis thanks for your reply, could you please take a look at the change? |
|
@ravbhatnagar New API version for Analysis Services. |
| "description": "The gateway details.", | ||
| "type": "object", | ||
| "properties": { | ||
| "gatewayResourceId": { |
There was a problem hiding this comment.
Is gateway resource exposed through ARM?
| } | ||
| } | ||
| }, | ||
| "/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.AnalysisServices/servers/{serverName}/listGatewayStatus": { |
There was a problem hiding this comment.
Why do you need a separate POST API to get the gateway status? Cant it be obtained by GET /servers/{servername}?
There was a problem hiding this comment.
By design, the spec can be found at section 3.9 of http://aka.ms/asarm/
Get /servers/{servername} only contains the gateway configuration info.
| "description": "Status of gateway is live", | ||
| "type": "object", | ||
| "properties": { | ||
| "status": { |
There was a problem hiding this comment.
What are the valid values for the status property? Can this be an enum?
| "description": "Gateway not live or not configured.", | ||
| "schema": { "$ref": "#/definitions/GatewayListStatusError" } | ||
| }, | ||
| "404": { |
There was a problem hiding this comment.
There could be other error codes that this API returns. So its best to capture the error conditions by defining a "default" response and including the error object definition in that.
There was a problem hiding this comment.
sure, will add default.
|
@sergey-shandar - SDK can start reviewing. |
| "description": "OK.", | ||
| "schema": { "$ref": "#/definitions/GatewayListStatusLive" } | ||
| }, | ||
| "400": { |
There was a problem hiding this comment.
If 4xx responses are supposed to throw an exception in generated code (it looks like that was the intention), they can unfortunately not be modeled like that but have to go into a default response. See https://github.com/Azure/azure-rest-api-specs/blob/current/documentation/creating-swagger.md#negative-responses for details. I'd recommend documenting status codes and their corresponding description in the description of the default response.
| "properties": { | ||
| "gatewayResourceId": { | ||
| "type": "string", | ||
| "description": "Gateway resource to be associated with the server. Only supported with api versions 2017-07-14 or higher." |
There was a problem hiding this comment.
Not sure whether it makes sense to document "Only supported with api versions 2017-07-14 or higher." - this very Swagger is tied to an API version, so it's kind of redundant information. On the other hand, you may have thought about what people read in docs generated from this Swagger (and I'm not sure how explicit API versions are called out in our auto-gened docs). But generally, I haven't seen this pattern before! @ravbhatnagar Guidance?
| } | ||
| } | ||
| }, | ||
| "GatewayErrors": { |
There was a problem hiding this comment.
Why is this called GatewayError*s*? It's used in a property called error and also by itself looks like it represents a single error.
| @@ -39,6 +39,24 @@ input-file: | |||
| - Microsoft.AnalysisServices/2016-05-16/analysisservices.json | |||
There was a problem hiding this comment.
Please flip order (most recent first). This has no influence on behavior, but makes it consistent with the other RP's configuration in this repo 🙂
|
Fixed, please take a look. |
| "enum": [ | ||
| "Live" | ||
| ], | ||
| "description": "Live message of list gateway." |
There was a problem hiding this comment.
add x-ms-enum part (set model as string to true)
olydis
left a comment
There was a problem hiding this comment.
Minor comment, but please take a look at the validation tool outputs: https://travis-ci.org/Azure/azure-rest-api-specs/jobs/263248184#L665
Is there anything you can resolve? Note that the x-ms-enum comment is one of the issues flagged by the validator, please review these issues.
|
Updated, the rest are all examples and operation list. |
| ``` yaml | ||
| openapi-type: arm | ||
| tag: package-2016-05 | ||
| tag: package-2017-07 |
There was a problem hiding this comment.
Could you change package-2017-07 to package-2017-08-beta so it refers to latest and #1542 can be closed.
| ``` yaml | ||
| openapi-type: arm | ||
| tag: package-2017-07 | ||
| tag: package-2017-07-08-beta |
There was a problem hiding this comment.
tag: package-2017-07-08-beta?
do you mean:
tag: package-2017-08-beta
|
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 and make AutoRest Linter Azure Bot smarter day by day! Thanks for your co-operation. |
|
@ravbhatnagar All your concerns addressed? |
| "pattern": "^[a-z][a-z0-9]*$", | ||
| "minLength": 3, | ||
| "maxLength": 63, | ||
| "description": "The name of the Analysis Services server. It must be at least 3 characters in length, and no more than 63." |
There was a problem hiding this comment.
Please remove It must be at least 3 characters in length, and no more than 63., don't restate constraints expressed in Swagger by other means.
There was a problem hiding this comment.
Sure, will do, but I just copy paste from previous one....
Can you just merge?
|
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 and make AutoRest Linter Azure Bot smarter day by day! Thanks for your co-operation. |
|
No modification for AutorestCI/azure-sdk-for-python |
|
No modification for AutorestCI/azure-sdk-for-node |
…d version 0801 (Azure#1526)" This reverts commit bf407b7.
* Revert "[Event Grid] Event grid C# code generation section. (#1561)" This reverts commit 461a494. * Revert "Bug Fix when linter runs on json file without being included in tag (#1560)" This reverts commit d6bc117. * Revert "Remove databaseName uri param from Databases_Import op. (#1558)" This reverts commit 69d0a5d. * Revert "Added 200 response for event grid event subscription delete operation. (#1555)" This reverts commit ad55af7. * Revert "Add some content to Swagger from docs.msft.com (#1549)" This reverts commit b955458. * Revert "[Azure Analysis Services] Add gateway info to version 0714 and version 0801 (#1526)" This reverts commit bf407b7. * Revert "Copied service endpoints specs to 2017-08-01 (#1548)" This reverts commit 64c905a. * Revert "Removed `x-ms-pageable` from Network Interface's `GetEffectiveRouteTable` and `ListEffectiveNetworkSecurityGroups` methods (#1547)" This reverts commit da940d5. * Revert "Added service endpoints APIs (#1533)" This reverts commit f69dc64. * Revert "Added support for ECC to Key Vault (#1538)" This reverts commit 4a9084f.
…re-rest-api-specs#1526) (#3616) * sdk for 2017-07-14 * Add recorded test * Updates csproj and test variable
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