Change statusMessage property to wildcard type.

[jhendrixMSFT]

The statusMessage can be a string or a JSON object, so model it as a
wildcard type.

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.

[jhendrixMSFT]

Fixes #2355.

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

AutoRest Linter Guidelines | AutoRest Linter Issues | Send feedback

Thanks for your co-operation.

[AutorestCI]

Automation for azure-sdk-for-python

A PR has been created for you:
Azure/azure-sdk-for-python#2003

[AutorestCI]

Automation for azure-sdk-for-go

Encountered a Subprocess error: (azure-sdk-for-go)

Command: dep ensure
Finished with return code 127
and output:

/bin/sh: 1: dep: not found

[jhendrixMSFT]

@vivsriaus can you please confirm this change applies to all API versions?

[vivsriaus]

@jhendrixMSFT thanks for making this change. Will this be considered a breaking change in SDK? How does the generated code look with these changes?

I'll confirm if this can apply to all API versions today.

[jhendrixMSFT]

@vivsriaus By luck this doesn't introduce any breaking changes while formalizing the behavior (see the linked issue for the details).

[jhendrixMSFT]

@sarangan12 can you please take a look at the Ruby build failure?

[vivsriaus]

thanks for making this change!

[sarangan12]

Reason for the Ruby CI Failure:

The root cause of this issue is this PR: #2469 This basically moved a folder to a different location. But, the swagger_to_sdk expects it in the old place. https://github.com/Azure/azure-sdk-for-ruby/blob/master/swagger_to_sdk_config.json#L1214 which is causing the error. I would recommend you to go ahead and merge it for now (if there are no other issues). I will fix the config