Skip to content

[Azure Analysis Services] Add gateway info to version 0714 and version 0801#1526

Merged
olydis merged 11 commits intoAzure:currentfrom
taiwu:taiwu-gw-89
Aug 17, 2017
Merged

[Azure Analysis Services] Add gateway info to version 0714 and version 0801#1526
olydis merged 11 commits intoAzure:currentfrom
taiwu:taiwu-gw-89

Conversation

@taiwu
Copy link
Copy Markdown
Contributor

@taiwu taiwu commented Aug 9, 2017

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

  • The title of the PR is clear and informative.
  • There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
  • Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
  • If applicable, the PR references the bug/issue that it fixes.
  • Swagger files are correctly named (e.g. the api-version in the path should match the api-version in the spec).

Quality of Swagger

@msftclas
Copy link
Copy Markdown

msftclas commented Aug 9, 2017

@taiwu,
Thanks for your contribution. It looks like you are a Microsoft vendor. To ensure that the project team has proper rights to use your work, please complete the Contribution License Agreement at https://cla.microsoft.com.

The agreement will cover your contributions to all Microsoft-managed open source projects.
Thanks,
Microsoft Pull Request Bot

@taiwu
Copy link
Copy Markdown
Contributor Author

taiwu commented Aug 9, 2017

Sync and add older version as requested in
#1518

@taiwu
Copy link
Copy Markdown
Contributor Author

taiwu commented Aug 9, 2017 via email

@olydis
Copy link
Copy Markdown
Contributor

olydis commented Aug 10, 2017

@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)

@taiwu
Copy link
Copy Markdown
Contributor Author

taiwu commented Aug 10, 2017

@olydis thanks for your reply, could you please take a look at the change?

@sergey-shandar sergey-shandar added the WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required label Aug 10, 2017
@sergey-shandar
Copy link
Copy Markdown
Contributor

@ravbhatnagar New API version for Analysis Services.

"description": "The gateway details.",
"type": "object",
"properties": {
"gatewayResourceId": {
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is gateway resource exposed through ARM?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes

}
}
},
"/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.AnalysisServices/servers/{serverName}/listGatewayStatus": {
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why do you need a separate POST API to get the gateway status? Cant it be obtained by GET /servers/{servername}?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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": {
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What are the valid values for the status property? Can this be an enum?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1

"description": "Gateway not live or not configured.",
"schema": { "$ref": "#/definitions/GatewayListStatusError" }
},
"404": {
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sure, will add default.

@ravbhatnagar ravbhatnagar added ReadyForSDKReview and removed WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required labels Aug 10, 2017
@ravbhatnagar
Copy link
Copy Markdown
Contributor

@sergey-shandar - SDK can start reviewing.

"description": "OK.",
"schema": { "$ref": "#/definitions/GatewayListStatusLive" }
},
"400": {
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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."
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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": {
Copy link
Copy Markdown
Contributor

@olydis olydis Aug 10, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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 🙂

Copy link
Copy Markdown
Contributor

@olydis olydis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

see comments

@taiwu
Copy link
Copy Markdown
Contributor Author

taiwu commented Aug 10, 2017

Fixed, please take a look.
Small adjustment, the v714 was a copy of v801, which is now based on v516.

"enum": [
"Live"
],
"description": "Live message of list gateway."
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

add x-ms-enum part (set model as string to true)

Copy link
Copy Markdown
Contributor

@olydis olydis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

@taiwu
Copy link
Copy Markdown
Contributor Author

taiwu commented Aug 14, 2017

Updated, the rest are all examples and operation list.
The latest build failure is not related to my latest commit.
@olydis could you please take a look?

``` yaml
openapi-type: arm
tag: package-2016-05
tag: package-2017-07
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

tag: package-2017-07-08-beta?
do you mean:
tag: package-2017-08-beta

@azuresdkciprbot
Copy link
Copy Markdown

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: specification/analysisservices/resource-manager/readme.md
Before the PR: Warning(s): 3 Error(s): 9
After the PR: Warning(s): 3 Error(s): 10

AutoRest Linter Guidelines | AutoRest Linter Issues

Send feedback and make AutoRest Linter Azure Bot smarter day by day!

Thanks for your co-operation.

@Azure Azure deleted a comment from azuresdkciprbot Aug 15, 2017
Copy link
Copy Markdown
Contributor

@olydis olydis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, descriptions of model types can be made consistently end with .

@olydis
Copy link
Copy Markdown
Contributor

olydis commented Aug 15, 2017

@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."
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sure, will do, but I just copy paste from previous one....
Can you just merge?

@azuresdkciprbot
Copy link
Copy Markdown

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: specification/analysisservices/resource-manager/readme.md
Before the PR: Warning(s): 3 Error(s): 9
After the PR: Warning(s): 3 Error(s): 10

AutoRest Linter Guidelines | AutoRest Linter Issues

Send feedback and make AutoRest Linter Azure Bot smarter day by day!

Thanks for your co-operation.

@ravbhatnagar ravbhatnagar added the ARMSignedOff <valid label in PR review process>add this label when ARM approve updates after review label Aug 16, 2017
@olydis olydis merged commit bf407b7 into Azure:current Aug 17, 2017
@AutorestCI
Copy link
Copy Markdown

No modification for AutorestCI/azure-sdk-for-python

@AutorestCI
Copy link
Copy Markdown

No modification for AutorestCI/azure-sdk-for-node

@AutorestCI
Copy link
Copy Markdown

schaabs pushed a commit to schaabs/azure-rest-api-specs that referenced this pull request Aug 18, 2017
olydis pushed a commit that referenced this pull request Aug 18, 2017
* 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.
shahabhijeet pushed a commit to Azure/azure-sdk-for-net that referenced this pull request Aug 29, 2017
…re-rest-api-specs#1526) (#3616)

* sdk for 2017-07-14

* Add recorded test

* Updates csproj and test variable
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ARMSignedOff <valid label in PR review process>add this label when ARM approve updates after review ReadyForSDKReview

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants