Skip to content

[ADLA - ADLS] - LRO PATCH#2013

Merged
sarangan12 merged 3 commits intoAzure:currentfrom
ro-joowan:lro-patch
Nov 15, 2017
Merged

[ADLA - ADLS] - LRO PATCH#2013
sarangan12 merged 3 commits intoAzure:currentfrom
ro-joowan:lro-patch

Conversation

@ro-joowan
Copy link
Copy Markdown
Contributor

@ro-joowan ro-joowan commented Nov 15, 2017 •
edited by azuresdkci
Loading

  • When updating ADLA/ADLS Accounts and the long-running-operation is triggered, the service currently returns 202 instead of 201, as stated in Swagger. Adding 202 here to patch this.

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

@azuresdkciprbot
Copy link
Copy Markdown

azuresdkciprbot commented Nov 15, 2017

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/datalake-analytics/data-plane/readme.md
Before the PR: Warning(s): 0 Error(s): 0
After the PR: Warning(s): 0 Error(s): 0

File: specification/datalake-analytics/resource-manager/readme.md
Before the PR: Warning(s): 0 Error(s): 6
After the PR: Warning(s): 0 Error(s): 6

File: specification/datalake-store/resource-manager/readme.md
Before the PR: Warning(s): 0 Error(s): 6
After the PR: Warning(s): 0 Error(s): 6

AutoRest Linter Guidelines | AutoRest Linter Issues | Send feedback

Thanks for your co-operation.

@azuresdkciprbot
Copy link
Copy Markdown

azuresdkciprbot commented Nov 15, 2017

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/datalake-analytics/data-plane/readme.md
Before the PR: Warning(s): 0 Error(s): 0
After the PR: Warning(s): 0 Error(s): 0

File: specification/datalake-analytics/resource-manager/readme.md
Before the PR: Warning(s): 0 Error(s): 6
After the PR: Warning(s): 0 Error(s): 6

File: specification/datalake-store/resource-manager/readme.md
Before the PR: Warning(s): 0 Error(s): 6
After the PR: Warning(s): 0 Error(s): 6

AutoRest Linter Guidelines | AutoRest Linter Issues | Send feedback

Thanks for your co-operation.

@sarangan12 sarangan12 merged commit 5e06f63 into Azure:current Nov 15, 2017
@ro-joowan ro-joowan deleted the lro-patch branch November 15, 2017 22:30
This was referenced Dec 15, 2017
Closed
Merged
Merged
mccleanp pushed a commit that referenced this pull request Mar 23, 2022
@ky-to
Add Azure Logistics's ARM APIs (#2013)
c39b5b2 
* Add Azure Logistics's ARM APIs

* Add example references

* Fix operation_list example files

* Update transportation provider type to the official types

* remove workspaceName

* remove unneeded properties from resource

* remove transportation providers

* Fix Operation_List example file

* Update Patch, its contract and example

* Add workspaceUrl and its examples

* Update examples of workspaceUrl to be have workspaceId without dash

* Minor updates and remove a few irrelevant contents

Co-authored-by: Ky To <kyt@microsoft.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

1 more reviewer

@sarangan12 sarangan12 sarangan12 approved these changes

Reviewers whose approvals may not affect merge requirements

Assignees

@sarangan12 sarangan12

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@ro-joowan @azuresdkciprbot @sarangan12