Add x-ms-azure-resource for tracked resource in event grid

[jianghaolu]

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-python

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

[AutorestCI]

Automation for azure-libraries-for-java

A PR has been created for you:
AutorestCI/azure-libraries-for-java#99

[AutorestCI]

Automation for azure-sdk-for-node

A PR has been created for you:
Azure/azure-sdk-for-node#2771

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

AutoRest Linter Guidelines | AutoRest Linter Issues | Send feedback

Thanks for your co-operation.

[AutorestCI]

Automation for azure-sdk-for-go

Nothing to generate for azure-sdk-for-go

[kalyanaj]

Thanks for the PR! A few questions just to make sure I fully understand this change:

1. Just to double-check, would this be a non-breaking change / won't impact the autorest generated SDK code?
2. Does this need to be added for types that derive from TrackedResource? ("Topic" is currently the only one)
3. Also, would it be also to use this PR to add this change to the 2018-05-01-preview version as well?

[jianghaolu]

Hi @kalyanaj
To answer your question - I don't believe this will be a breaking change but I could be wrong. The types deriving from this won't need it.

Let me sync up with the guy on my team generating the SDK. Maybe we will be okay just adding this to 2018-05-01-preview.