[Compute] Add VmssVM PUT API.

[hyonholee]

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.

[anuchandy]

Addition of settable properties to an existing model (VirtualMachineScaleSetVMProfile) of an existing api version is considered as breaking change.

It looks like this model VirtualMachineScaleSetVMProfile is used in VirtualMachineScaleSet model [VirtualMachineScaleSet -> VirtualMachineScaleSetProperties -> VirtualMachineScaleSetVMProfile] which represent payload of already supported VMSS create or update op. that means we are adding settable properties to VMSS create_update payload.

Adding ARM to review this.

[anuchandy]

@ravbhatnagar please take a look

[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:

💡 Please review potentially introduced Error(s)/Warning(s): Analysis Report 💡

File: specification/compute/resource-manager/readme.md
Before the PR: Warning(s): 0 Error(s): 32
After the PR: Warning(s): 0 Error(s): 33

AutoRest Linter Guidelines | AutoRest Linter Issues | Send feedback

Thanks for your co-operation.

[ravbhatnagar]

Add the final 200 OK response also under "responses".

[ravbhatnagar]

This requires an API-version change as a new writable property is getting added.

[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/compute/resource-manager/readme.md
Before the PR: Warning(s): 0 Error(s): 32
After the PR: Warning(s): 0 Error(s): 32

AutoRest Linter Guidelines | AutoRest Linter Issues | Send feedback

Thanks for your co-operation.

[anuchandy]

@hyonholee what's the plan here? are we going to bump up the api version based on Gaurav's comment?

[hyonholee]

@anuchandy I removed the priority part, which Gaurav said requires API version update. Now this PR only contains VMSSVM PUT operation. This is additional operation and does not modify existing API, so does not require API version update.

[hyonholee]

@anuchandy For priority, I will send a separate PR after we resolve the issue.

[anuchandy]

@ravbhatnagar PR looks good to me, can you please sign-off?

[ravbhatnagar]

Signing off!

[hyonholee]

@anuchandy Please merge this PR. I will send a separate PR for priority right after this PR is merged. Thanks.

[anuchandy]

Thanks @ravbhatnagar. @hyonholee merging.

[AutorestCI]

Azure/azure-sdk-for-ruby#1222

[AutorestCI]

Azure/azure-sdk-for-python#1742