Update SQL VM Rest API

[sam0227]

Latest improvements:

MSFT employees can try out our new experience at OpenAPI Hub - one location for using our validation tools and finding your workflow.

Contribution checklist:

• I have reviewed the documentation for the workflow.
• Validation tools were run on swagger spec(s) and have all been fixed in this PR.
• The OpenAPI Hub was used for checking validation status and next steps.

ARM API Review Checklist

• Service team MUST add the "WaitForARMFeedback" label if the management plane API changes fall into one of the below categories.
• adding/removing APIs.
• adding/removing properties.
• adding/removing API-version.
• adding a new service in Azure.

Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.

• If you are blocked on ARM review and want to get the PR merged urgently, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
  Please follow the link to find more details on API review process.

[openapi-sdkautomation]

In Testing, Please Ignore

[Logs] (Generated from c7976a7, Iteration 14)

.NET: test-repo-billy/azure-sdk-for-net [Logs] [Diff]

• Microsoft.Azure.Management.SqlVirtualMachine [Logs] [Instructions]
  • Microsoft.Azure.Management.SqlVirtualMachine.1.0.0.nupkg
  • Microsoft.Azure.Management.SqlVirtualMachine.1.0.0.snupkg

Python: test-repo-billy/azure-sdk-for-python [Logs] [Diff]

• azure-mgmt-sqlvirtualmachine [Logs] [Instructions] [Generation PR] [Integration PR]
  • azure-mgmt-sqlvirtualmachine-0.4.0.zip
  • azure_mgmt_sqlvirtualmachine-0.4.0-py2.py3-none-any.whl

Go: test-repo-billy/azure-sdk-for-go [Logs] [Diff]

• preview/sqlvirtualmachine/mgmt/2017-03-01-preview [Logs] [Instructions] [Generation PR] [Integration PR]
  • preview.sqlvirtualmachine.mgmt.2017-03-01-preview.zip

Java: test-repo-billy/azure-sdk-for-java [Logs] [Diff]

• sqlvirtualmachine/resource-manager/v2017_03_01_preview [Logs] [Instructions]
  • pom.xml
  • azure-mgmt-sqlvirtualmachine-1.0.0-beta-javadoc.jar
  • azure-mgmt-sqlvirtualmachine-1.0.0-beta-sources.jar
  • azure-mgmt-sqlvirtualmachine-1.0.0-beta.jar

[AutorestCI]

Automation for azure-sdk-for-go

The initial PR has been merged into your service PR:
Azure/azure-sdk-for-go#5950

[AutorestCI]

Automation for azure-sdk-for-python

The initial PR has been merged into your service PR:
Azure/azure-sdk-for-python#7609

[azuresdkci]

Can one of the admins verify this patch?

[PhoenixHe-NV]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 2 pipeline(s).

[lirenhe]

@sam0227 , could you check the model validation error and fix the issue?

[nschonni]

You could add "LUNs" to ./custom-words.txt to fix the other spelling issues

[sam0227]

@lirenhe Fixed the issues.

[ravbhatnagar]

@sam0227 - Adding new writable properties to an existing API-version is a breaking change. It must be done in a new api-version. WHat is the impact of this property being set using for example portal, and then fetched by doing GET from an older SDK which does not understand this property (hence ignores it). And then PUT from the older SDK without this property on the same resource which has this property set. Will the service overwrite the goal state.
Since its preview, it may be ok, but please note that customers can still be broken or can make unintentional breaking changes to the resource.

[sam0227]

@ravbhatnagar These properties allow the user to configure the storage pool related to SQL. If the properties are not set it'll be no-op so it should have no impact if someone do GET and PUT are from older SDK. We don't have a plan for a new API version for now.

@vasivara-MSFT Add Vairavan who owns the list sqlvm operation

[ravbhatnagar]

SIgning off from ARM side. RP implementation is not a true PUT and so it will not cause unintentional destructive behavior for customers.