EventGrid: Update README files to include the current new preview api…

[ahamad-MS]

… version 2018-09-preview

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

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

[AutorestCI]

Automation for azure-sdk-for-js

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

[AutorestCI]

Automation for azure-sdk-for-go

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

[azuresdkci]

Can one of the admins verify this patch?

[AutorestCI]

Automation for azure-sdk-for-node

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

[kalyanaj]

Looking at the latest readme.me in the master, it looks like the Go configuration has been branched out to a separate file. It looks like you need to sync those changes in your branch and this change needs to happen in the GO specific readme file.

[kalyanaj]

The linter error is a known issue in the ARM validation: Azure/azure-openapi-arm-validator#10.

[praries880]

@azuresdkci add to whitelist

[kalyanaj]

LGTM.

[kalyanaj]

@praries880, the "Automation for azure-sdk-for-go" CI step seems to be failing, however reviewing the readme.go.md file, the keys seem to be unique and we can't find what the issue is. Can you please help us with this issue?

[praries880]

@ahamad-MS you need to fix the ARM validation error : https://github.com/Azure/azure-rest-api-specs/pull/4235/checks?check_run_id=23938472 to get green on the CI

Heres the error :

	R3026 - TrackedResourcePatchOperation	2018-09-15-preview/​EventGrid.json:2134	Tracked resource 'Domain' must have patch operation that at least supports the update of tags. It's strongly recommended that the PATCH operation supports update of all mutable properties as well.

@veronicagg Do you know why was the linter error in the json not caught earlier?

[kalyanaj]

@praries880, please see my earlier comment above: the linter error is a known issue in the ARM validation: Azure/azure-openapi-arm-validator#10 and is being tracked by the ARM team.

[praries880]

@jhendrixMSFT Can you help merge the PR in? I seem to lack the required permissions.