Skip to content

[ADLA - ADLS] - Adding existing account APIs that are missing in Swagger#1807

Merged
anuchandy merged 3 commits intoAzure:currentfrom
ro-joowan:missing-account-apis
Oct 11, 2017
Merged

[ADLA - ADLS] - Adding existing account APIs that are missing in Swagger#1807
anuchandy merged 3 commits intoAzure:currentfrom
ro-joowan:missing-account-apis

Conversation

@ro-joowan
Copy link
Copy Markdown
Contributor

@ro-joowan ro-joowan commented Oct 5, 2017

  • Added the following existing APIs

    • Account_CheckNameAvailability
    • Location_GetCapability
    • Operation_List
  • Successfully tested these APIs by generating the C# SDK and executing them

  • Added example files for these APIs

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

Copy link
Copy Markdown
Member

@anuchandy anuchandy left a comment

Choose a reason for hiding this comment

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

@ro-joowan, overall looks good, added some minor feedback, please take a look.

Given that you are just adding existing APIs to the swagger, I am assuming these APIs are approved by ARM review board, right?

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

In order to be consistent with tag, operationId naming convention, use tag as Accounts and operationId as Accounts_CheckNameAvailability.

Copy link
Copy Markdown
Contributor Author

@ro-joowan ro-joowan Oct 9, 2017

Choose a reason for hiding this comment

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

For this one I would like to leave as is for this PR because we currently have existing APIs for "Account_Get", "Account_Create", etc. We will make the fix to "Accounts" in an upcoming API version, 2017-10-01, which has other breaking changes -- as we would like to bundle the breaking changes together.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

tags -> Locations, operationId -> Locations_GetCapability

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.

Fixed -- thank you!

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

tags -> Locations, operationId -> Locations_List

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.

Fixed -- thank you!

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Account ->Accounts, Account_CheckNameAvailability -> Accounts_CheckNameAvailability

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.

For this one I would like to leave as is for this PR because we currently have existing APIs for "Account_Get", "Account_Create", etc. We will make the fix to "Accounts" in an upcoming API version, 2017-10-01, which has other breaking changes -- as we would like to bundle the breaking changes together.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

use {plural}_{verb}

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.

Fixed -- thank you!

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

use {plural}_{verb}

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.

Fixed -- thank you!

* Added the following existing APIs
* Account_CheckNameAvailability
* Location_GetCapability
* Operation_List

* Successfully tested these APIs by generating the C# SDK and executing
them

* Added example files for these APIs
@ro-joowan ro-joowan force-pushed the missing-account-apis branch from 98fca31 to 6c0a28b Compare October 9, 2017 18:07
@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/datalake-analytics/resource-manager/readme.md
Before the PR: Warning(s): 0 Error(s): 7
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): 7
After the PR: Warning(s): 0 Error(s): 6

AutoRest Linter Guidelines | AutoRest Linter Issues | Send feedback

Thanks for your co-operation.

@ro-joowan
Copy link
Copy Markdown
Contributor Author

ro-joowan commented Oct 9, 2017

@anuchandy, These APIs that I am adding were requested by the ARM team for us to add and other services have these exact APIs already.

Thank you!

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

AutoRest Linter Guidelines | AutoRest Linter Issues | Send feedback

Thanks for your co-operation.

1 similar comment
@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/datalake-analytics/resource-manager/readme.md
Before the PR: Warning(s): 0 Error(s): 7
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): 7
After the PR: Warning(s): 0 Error(s): 6

AutoRest Linter Guidelines | AutoRest Linter Issues | Send feedback

Thanks for your co-operation.

@ro-joowan
Copy link
Copy Markdown
Contributor Author

@anuchandy, Also, could you please provide a link where it says that we should use {plural}_{verb}? This was a question we had internally, and the link would be a helpful reference for us in the future.

@anuchandy
Copy link
Copy Markdown
Member

@ro-joowan sorry this is not documented. I checked with few reviewers, this is not a hard requirement but nice to have a consistency. Some of the reason for choosing plural are -

  1. If the segment in the endpoint pointing to the collection is plural then it is good to use the similar name for the operation group. e.g. the root url for operation on availability set is /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Compute/availabilitySets/..." so it is recommended to have the operation group name as AvailabilitySets

  2. It is not allowed to have the same name for both operation group and model name. In such cases it is recommended to use plural for the operation group name https://github.com/Azure/azure-rest-api-specs/blob/current/documentation/openapi-authoring-automated-guidelines.md#r2063-operationidnounconflictingmodelnames.

@ro-joowan
Copy link
Copy Markdown
Contributor Author

@anuchandy Thank you for that. Can we proceed with the merge?

@anuchandy
Copy link
Copy Markdown
Member

@ro-joowan sure, merging..

@anuchandy anuchandy merged commit de178f7 into Azure:current Oct 11, 2017
@AutorestCI
Copy link
Copy Markdown

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

@AutorestCI
Copy link
Copy Markdown

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants