Fix for a linter error related to default value in PATCH request body + use the correct default value in PUT

[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.

1. Fix for a linter error: "Properties of a PATCH request body must not be default-valued. PATCH operation: 'EventSubscriptions_Update' Model Definition: 'EventSubscriptionUpdateParameters' Property: 'eventDeliverySchema'".
2. [Non-breaking change] Fixing a bug in the Swagger in this preview API version where the mentioned default value for EventDeliverySchema didn't reflect the actual default value used by the service. Should have no effect on generated SDK code.

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

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

[AutorestCI]

Automation for azure-sdk-for-java

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

[AutorestCI]

Automation for azure-sdk-for-go

Nothing to generate for azure-sdk-for-go

[AutorestCI]

Automation for azure-sdk-for-ruby

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

[annatisch]

Thanks @kalyanaj!
I see there's still an additional linter error - is there a plan to resolve this one as well?

"Tracked resource 'Topic' 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."

There's also a couple of model validation errors in the following samples:

• EventSubscriptions_GetForResource
• EventSubscriptions_ListRegionalBySubscription

[kalyanaj]

@annatisch , regarding the additional linter error, that's an issue in the linter/validation tools, and it is being tracked by Azure/azure-openapi-arm-validator#10.

I will take a look at the model validation errors.

[kalyanaj]

@annatisch, can I submit the fixes for the existing model validation errors in EventSubscriptions_GetForResource and EventSubscriptions_ListRegionalBySubscription in a separate pull request? As I am travelling this week, I would like to request that this current PR that covers the fix for the other unrelated linter issue get merged first to address the linter issue.

[annatisch]

Okay - I will follow up next week :)