WebApps - Add ResourceHealthMetadata.json to readme.md for SDK generation

[nking-1]

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.

[AutorestCI]

Automation for azure-sdk-for-ruby

Nothing to generate for azure-sdk-for-ruby

[AutorestCI]

Automation for azure-sdk-for-python

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

[azuresdkci]

Can one of the admins verify this patch?

[AutorestCI]

Automation for azure-sdk-for-go

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

[AutorestCI]

Automation for azure-sdk-for-java

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

[AutorestCI]

Automation for azure-sdk-for-node

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

[jhendrixMSFT]

Close then re-open to hopefully fix CI.

[nking-1]

@jhendrixMSFT I made an additional change to fix some problems with the generated SDK. The deleted web app model was not correct in the swagger which broke our APIs in SDKs / Powershell.

[jhendrixMSFT]

Waiting for CI to finish.

[panchagnula]

@jhendrixMSFT , I see that Linter Diff never completes & looking at the details there a some warnings reported. However, we are unable to parse if the new warning from the existing ones - can you help us identify the warning specific to this change? Thank you.

[jhendrixMSFT]

@panchagnula I spoke with the CI owners about this, it's a known issue that they're working on. In the meantime take a look at the log and search for ResourceHealthMetadata.json to see the warning introduced by this swagger.

[nking-1]

After reviewing the new warnings, I can say we are OK with taking the current swagger as-is. None of the warnings were for critical issues. The devs for those APIs will fix them in the future. The timeline for that dev work is out of scope for our deadlines for the new SDKs, so we'd like to take this swagger update to unblock short-term work.