[ADLA] - Adding Scope APIs/Properties, existing Catalog APIs, and existing Account APIs

[ro-joowan]

• I did not add unit tests for anything related to Scope. These APIs/properties are for internal use only, as noted in their descriptions, and we have internal tests for them.

REST spec PR link to the SDK PR

• [ADLA - ADLS] - LRO PATCH azure-rest-api-specs#2013
• [ADLA] - Adding existing Catalog ACL APIs azure-rest-api-specs#1952
• [ADLA - ADLS] - [BUGFIX] - Fixing x-ms-odata parameters azure-rest-api-specs#1857
• [ADLA] - Removing trailing slash for a couple LIST APIs azure-rest-api-specs#1848
• [ADLA] - Fixing YieldJob API path azure-rest-api-specs#1842
• [ADLA - ADLS] - Adding existing account APIs that are missing in Swagger azure-rest-api-specs#1807
• Scope2 azure-rest-api-specs#1745

[ADLA] Changes in 3.2.3-preview

Breaking changes

• Changed the ODataQuery parameter type from DataLakeAnalyticsAccount to DataLakeAnalyticsAccountBasic for these APIs:
  • Account_List
  • Account_ListByResourceGroup
• For USqlJobProperties, fixed the property name of TotalPauseTime to TotalPausedTime

Notes

• Added more properties to JobStatisticsVertexStage
• Added two more states to DataLakeAnalyticsAccountStatus enum: Undeleting and Canceled
• Added new Account APIs:
  • Account_CheckNameAvailability
  • Location_GetCapability
  • Operation_List
• Added new Catalog APIs:
  • Catalog_ListAclsByDatabase
  • Catalog_ListAcls
  • Catalog_GrantAclToDatabase
  • Catalog_RevokeAclFromDatabase
  • Catalog_GrantAcl
  • Catalog_RevokeAcl

Description

---

This checklist is used to make sure that common guidelines for a pull request are followed.

• Please add REST spec PR link to the SDK PR
• I have read the contribution guidelines.
• The pull request does not introduce breaking changes.

General Guidelines

• Title of the pull request 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 more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

• Pull request includes test coverage for the included changes.

SDK Generation Guidelines

• If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
• The generate.cmd file for the SDK has been updated with the version of AutoRest, as well as the commitid of your swagger spec or link to the swagger spec, used to generate the code.
• The *.csproj and AssemblyInfo.cs files have been updated with the new version of the SDK.

[shahabhijeet]

1. Get latest updates from upstream (if you have not done so in last 3 weeks)
2. Then execute msbuild build.proj to update your build tools
3. Then regenerate your SDK (this will regenerate couple of additional files, this file is required and usually starts with SDK_*.cs
4. build you project (ether IDE or command line, this will create addition file *.props. This file is also reqired)
5. Then update your PR
   With the latest changes, every regeneration will generate couple of additional meta data files that are needed in each PR.

[ro-joowan]

@shahabhijeet I followed those steps already as you noted them in my initial PR: #3954

I did notice one extra file being generated when I built the project using the IDE, which I did not include here

[shahabhijeet]

@ro-joowan those files required. See my previous comment where I specified which step will create which file and all those files are required.

[ro-joowan]

@shahabhijeet Thank you pointing them out in detail! The process makes more sense now. I have updated this PR.

[ro-joowan]

@shahabhijeet Not sure why Travis failed, is there a way to restart?

[shahabhijeet]

This PR looks good, once the CI passes this is good to be merged