Skip to content

[Azure Analysis Services] Add dissociate gateway operation#1625

Merged
olydis merged 1 commit intoAzure:currentfrom
taiwu:taiwu-gw-del
Sep 21, 2017
Merged

[Azure Analysis Services] Add dissociate gateway operation#1625
olydis merged 1 commit intoAzure:currentfrom
taiwu:taiwu-gw-del

Conversation

@taiwu
Copy link
Copy Markdown
Contributor

@taiwu taiwu commented Aug 31, 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

@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

@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): 0 Error(s): 0
After the PR: Warning(s): 0 Error(s): 0

AutoRest Linter Guidelines | AutoRest Linter Issues

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

Thanks for your co-operation.

@olydis olydis added the WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required label Sep 1, 2017
@olydis
Copy link
Copy Markdown
Contributor

olydis commented Sep 1, 2017

@ravbhatnagar new operation

Copy link
Copy Markdown
Contributor

@ravbhatnagar ravbhatnagar left a comment

Choose a reason for hiding this comment

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

@taiwu - Need to understand the intent of this API little more.

}
}
},
"/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.AnalysisServices/servers/{serverName}/dissociateGateway": {
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.

how will calling this API change the payload of the GET /servers/{serverName} existing API that you have? THat has a gatewayResourceId which is associated with the server. What does disassociating that gateway mean?

@taiwu
Copy link
Copy Markdown
Contributor Author

taiwu commented Sep 6, 2017 via email

@salameer
Copy link
Copy Markdown
Member

@taiwu and @ravbhatnagar any updates on this PR?

@taiwu
Copy link
Copy Markdown
Contributor Author

taiwu commented Sep 15, 2017

@ravbhatnagar as mentioned, the gatewayDetails object in get is mutable property.
If the AS instance dissociate the gateway, the AS instance will not have gatewayDetails object.

@olydis
Copy link
Copy Markdown
Contributor

olydis commented Sep 20, 2017

@ravbhatnagar ping

@ravbhatnagar
Copy link
Copy Markdown
Contributor

@olydis - Following up with @taiwu on IM. This ideally should be modelled through a PUT and a new POST API should not be needed.

@ravbhatnagar
Copy link
Copy Markdown
Contributor

As per email conversation and ACK from AS team, we will let this PR in with the understanding that the team will fix this in the new API-version revision. This behavior is already implemented in the service side.
@johanste @salameer as FYI.
@olydis - Good to merge the PR,

@ravbhatnagar
Copy link
Copy Markdown
Contributor

@veronicagg - we need a new label to mark such PRs which we have conditionally merged. It will help in pulling them later and following up with the teams.

@ravbhatnagar ravbhatnagar added ARMSignedOff <valid label in PR review process>add this label when ARM approve updates after review and removed WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required labels Sep 21, 2017
@olydis olydis merged commit 48c7271 into Azure:current Sep 21, 2017
@AutorestCI
Copy link
Copy Markdown

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

@AutorestCI
Copy link
Copy Markdown

@veronicagg
Copy link
Copy Markdown
Contributor

@ravbhatnagar sure, I didn't know we were doing conditional merges. How will this work from the point of view of generating SDKs and breaking changes? Label is not a problem, I can create "Conditionally-Merged" label, feel free to use it, but I'm curious on how we're dealing with these after the conditional merge.

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 Conditionally-Merged

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants