Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

EventGrid: Regenerate new SDK for 2019-01-01 Api Version #5097

Closed
wants to merge 13 commits into from

Conversation

ahamad-MS
Copy link
Contributor

@ahamad-MS ahamad-MS commented Dec 18, 2018

Description

Regenerate new SDK for API Version 2019-01-01 based off the following new Swagger Spec: Azure/azure-rest-api-specs#4899

This checklist is used to make sure that common guidelines for a pull request are followed.

General Guidelines

  • Title of the pull request 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 more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

  • Pull request includes test coverage for the included changes.

SDK Generation Guidelines

  • If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
    Event Grid 2019-01-01 API Version: Swagger and related test examples azure-rest-api-specs#4899

  • The generate.cmd file for the SDK has been updated with the version of AutoRest, as well as the commitid of your swagger spec or link to the swagger spec, used to generate the code.

  • The *.csproj and AssemblyInfo.cs files have been updated with the new version of the SDK.

@@ -17,6 +17,6 @@

[assembly: ComVisible(false)]

[assembly: AssemblyVersion("1.0.0.0")]
[assembly: AssemblyFileVersion("1.0.0.0")]
[assembly: AssemblyVersion("2.0.0.0")]
Copy link
Contributor

@kalyanaj kalyanaj Dec 18, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This change in this file should be reverted - since this is the dataplane test AssemblyInfo, I don't think we need an assembly version update for this one.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fixed

@@ -8,8 +8,8 @@
[assembly: AssemblyTitle("Microsoft Azure EventGrid Library")]
[assembly: AssemblyDescription("Provides developers with a library to publish events to Azure EventGrid and to consume events delivered by EventGrid.")]

[assembly: AssemblyVersion("3.0.0.0")]
[assembly: AssemblyFileVersion("3.0.0.0")]
[assembly: AssemblyVersion("4.0.0.0")]
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The change in this file should be reverted as this is the dataplane assemblyinfo.

Copy link
Contributor Author

@ahamad-MS ahamad-MS Dec 18, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fixed

<AssemblyName>Microsoft.Azure.Management.EventGrid</AssemblyName>
<PackageTags>Microsoft Azure EventGrid Management;Event Grid;Event Grid management;</PackageTags>
<PackageReleaseNotes>Taking dependency on 10.0.3 version of Newtonsoft nuget package.</PackageReleaseNotes>
<PackageReleaseNotes>Introducing 2019-01-01 as new GA API version.</PackageReleaseNotes>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggest replacing this with "This corresponds to the 2019-01-01 stable API version that supports General Availability of the following functionality related to event subscriptions: DeadLetter destination, Storage queue as destination, HybridConnection as destination, manual handshake validation, and support for retry policies. Features that are still in preview (such as Event Grid domains or advanced filters support) can still be accessed using the 3.0.1-preview version of the SDK."

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fixed

@ahamad-MS
Copy link
Contributor Author

ahamad-MS commented Dec 18, 2018

@dsgouda
@shahabhijeet

Can you please take a look at this PR or suggest someone? thx

Copy link
Member

@shahabhijeet shahabhijeet left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please rebase and clean up your commits. Keep logical commits in the history.
Also use generate.ps1 to generate your SDK. You are missing meta data that get's generated as part of the SDK generation process.

@@ -17,6 +17,6 @@

[assembly: ComVisible(false)]

[assembly: AssemblyVersion("1.0.0.0")]
[assembly: AssemblyFileVersion("1.0.0.0")]
[assembly: AssemblyVersion("2.0.0.0")]
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ahamad-MS this is not required, you are never going to release your test nuget package.
Please undo this change, adds unnecessary commit history to the file.
Unless you have a very specific reason to bump up test assembly version.

@ahamad-MS
Copy link
Contributor Author

Restarting new PR with fewer commits

@ahamad-MS ahamad-MS deleted the psSdkJson6 branch February 26, 2019 22:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants