New API Version 2017-08-01: Adding Sku property into publicIP and loa…

[gmainar]

…d balancer (#1528)

• Updating documentation for Microsoft.VisualStudio with project resource APIs. Corrections to existing examples. (Updating documentation for Microsoft.VisualStudio with project resour… #1498)

• Added Api-Version 2017-07-01 for RecoveryServices.Backup Jobs (Added Api-Version 2017-07-01 for RecoveryServices.Backup Jobs #1502)

• Added Api-Version 2017-07-01 for RecoveryServices.Backup Jobs

• Updated tag names

• Microsoft.Sql - Added data sync to package-2015-05-preview (Microsoft.Sql - Added data sync to package-2015-05-preview #1510)

• Added advisors and data sync to package-2015-05-preview

• Removed advisors so current branch is only data sync

• Make MsDeploy and MsDeployLog Azure resources (Make MsDeploy and MsDeployLog Azure resources #1519)

• Add public certificates, Functions Admin Token and MSDeploy APIs

• Revert resource definition changes and description change for site properties

• Make type and name readonly properties. Add ARM envelope to MSDeployStatus object

• Fix missing quotation issue.

• Add long running operation to MS deploy

• Make MsDeploy and MsDeployLog Azure resources

• Fix some AutoRest validation issues. Use dictionary for msdeploy.setparameters

• Ensure models are same across all schemas in Microsoft.Web

• Fix azure resource type across all models

• Remove conflicting ListOperations. It is not used for public Azure.

• no YAML in glob patterns for report scripts

• Copying 2017-06-01 to 2017-08-01

• Changes for new API version

• Updated script to run autorest with grouping swaggers based on config file (Updated getStatus to run autorest with grouping swaggers based on config file #1529)

• Removed the maxLength for entities (ServiceBus: Removed the maxLength for entity names #1527)

• Update folder structure example. (Update folder structure example. #1489)

Agreed on the changes

• [Travis-ci] Oad in ci status ([Travis-ci] Oad in ci status #1520)

• Breaking change build should fail if result contains error
  Skipping newly added files
  Incorporating review feedback

• testing

• log the result as oad.compare returns promise for caller

• Use published oad

• Revert "testing"

This reverts commit a9be94d.

• Removed maxLength from entity name (EventHub: Removed the maxLength for entity names #1531)

• This is to add Cognitive Services data-plane API specs starting with Face API. (This is to add Cognitive Services data-plane API specs starting with Face API. #1467)

• Adding data plane spec starting with Face

• Move Spec to right folder

• Fixing validation issues.

• Fixing issues and adding a readme.md

• Fixing examples by removing decimals.

• Removing another decimal value

• Update readme.md

• Updating spec based on comments.

• Removing .gitignore.

• Relay: Removed the maxLength for entity names (Relay: Removed the maxLength for entity names #1535)

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

• I have read the contribution guidelines.
• My spec meets the review criteria:
  • The spec conforms to the Swagger 2.0 specification.
  • The spec follows the guidelines described in the Swagger checklist document.
  • Validation tools were run on swagger spec(s) and have all been fixed in this PR.

[msftclas]

@gmainar,
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

[gmainar]

@anuchandy , can you please merge?

[AutorestCI]

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

[azuresdkciprbot]

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/network/resource-manager/readme.md
Before the PR: Warning(s): 150 Error(s): 83
After the PR: Warning(s): 151 Error(s): 83

AutoRest Linter Guidelines | AutoRest Linter Issues

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

Thanks for your co-operation.

[AutorestCI]

Azure/azure-sdk-for-ruby#894

[AutorestCI]

Azure/azure-sdk-for-python#1366