Adding tests for the changes in swagger api spec for patch status in VMInstanceView, properties in AssessPatches API and patch settings in Windows and Linux Configuration in VMModel

[rane-rajasi]

…VMInstanceView, properties in AssessPatches API and patch settings in Windows and Linux Configuration in VMModel

PR for related swagger changes: Azure/azure-rest-api-specs#11768 and Azure/azure-rest-api-specs#12295

[check-enforcer]

This pull request is protected by Check Enforcer.

What is Check Enforcer?

Check Enforcer helps ensure all pull requests are covered by at least one check-run (typically an Azure Pipeline). When all check-runs associated with this pull request pass then Check Enforcer itself will pass.

Why am I getting this message?

You are getting this message because Check Enforcer did not detect any check-runs being associated with this pull request within five minutes. This may indicate that your pull request is not covered by any pipelines and so Check Enforcer is correctly blocking the pull request being merged.

What should I do now?

If the check-enforcer check-run is not passing and all other check-runs associated with this PR are passing (excluding license-cla) then you could try telling Check Enforcer to evaluate your pull request again. You can do this by adding a comment to this pull request as follows:
/check-enforcer evaluate
Typically evaulation only takes a few seconds. If you know that your pull request is not covered by a pipeline and this is expected you can override Check Enforcer using the following command:
/check-enforcer override
Note that using the override command triggers alerts so that follow-up investigations can occur (PRs still need to be approved as normal).

What if I am onboarding a new service?

Often, new services do not have validation pipelines associated with them, in order to bootstrap pipelines for a new service, you can issue the following command as a pull request comment:
/azp run prepare-pipelines
This will run a pipeline that analyzes the source tree and creates the pipelines necessary to build and validate your pull request. Once the pipeline has been created you can trigger the pipeline using the following comment:
/azp run net - [service] - ci

[YalinLi0312]

@rane-rajasi Please make sure the related swagger PR gets merged, otherwise I can't start my review.

[rane-rajasi]

Related swagger PR is now merged

[YalinLi0312]

@rane-rajasi I don't see updates in metadata, versions, and so on. Could you please follow the checklist below?

• Swagger review PR(s) link in PR description, and the PR(s) is merged
• Metadata file eng/mgmt/mgmtmetadata_{RP}.txt is updated
• Versions in *.csproj and AssemblyInfo.cs are updated, and follows semver
• Release notes in *.csproj is updated
• If there's a API-version update, the API tags in Az.Sdk.props are updated
• Generated code is not touched
• Proper test coverage

[YalinLi0312]

@rane-rajasi If no updates, will close it next week. Thanks

[rane-rajasi]

Please follow up with Adam Sandor for updates regarding this PR. Since it is in compute-2020-12, Adam will have more details on the PR

[Sandido]

Closing for now.

[rane-rajasi]

@Sandido Updated the PR with latest from compute-2020-12. Please review