Swagger definitions for the schemas of the Event Grid events published by Azure Storage and Azure EventHub services.

[kalyanaj]

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.

[alvadb]

Please review the linter errors: https://travis-ci.org/Azure/azure-rest-api-specs/jobs/316049515

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

AutoRest Linter Guidelines | AutoRest Linter Issues | Send feedback

Thanks for your co-operation.

[kalyanaj]

@alvadb, regarding the linter error, the error is "Error: No unique 'title' across OpenAPI definitions:", however in this case they are three separate Swagger definitions so the titles being unique is by design. (This is somewhat similar to the model of https://github.com/Azure/azure-rest-api-specs/blob/master/specification/compute/resource-manager/readme.md where multiple swagger definition files are included in the same autorest configuration file in readme.md).

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

AutoRest Linter Guidelines | AutoRest Linter Issues | Send feedback

Thanks for your co-operation.

[kalyanaj]

@alvadb, can you please take a look at this PR? Please see my comments above related to the 1 linter error. Thanks!

[alvadb]

I seem to have lost permission to merge. I will look into this and hope to get this merged tomorrow.

[AutorestCI]

No modification for AutorestCI/azure-sdk-for-python

[AutorestCI]

No modification for AutorestCI/azure-sdk-for-ruby