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

Expose new SKUs for VirtualNetworkGateway ER and VPN VMSS #4322

Closed
wants to merge 2 commits into from
Closed

Expose new SKUs for VirtualNetworkGateway ER and VPN VMSS #4322

wants to merge 2 commits into from

Conversation

ritwikbasu
Copy link
Contributor

@ritwikbasu ritwikbasu commented May 15, 2018

Expose new SKUs for VirtualNetworkGateway ER and VPN VMSS

Description


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

Expose new SKUs for VirtualNetworkGateway ER and VPN VMSS
@ritwikbasu
Copy link
Contributor Author

The REST-API PR is Azure/azure-rest-api-specs#3069

Copy link
Contributor

@dsgouda dsgouda left a comment

Choose a reason for hiding this comment

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

Please generate the code using generate.ps1 script and commit changes to the .txt log file

@@ -7,7 +7,7 @@
<PackageId>Microsoft.Azure.Management.Network</PackageId>
<Description>Provides management capabilities for Network services.</Description>
<AssemblyName>Microsoft.Azure.Management.Network</AssemblyName>
<Version>19.0.0-preview</Version>
Copy link
Contributor

Choose a reason for hiding this comment

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

This does not look like a breaking change. You can simply set it as 19.0.1-preview instead

Copy link
Contributor

Choose a reason for hiding this comment

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

Also, update the PackageReleaseNotes

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 in second commit.

Review Comments
Copy link
Contributor

@dsgouda dsgouda left a comment

Choose a reason for hiding this comment

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

LGTM

@dsgouda
Copy link
Contributor

dsgouda commented May 15, 2018

Will merge on CIs passing


1) azure-rest-api-specs repository information
GitHub user: Azure
Branch: master
Commit: b9721ae4c9f04914cc89260b8339dc33372f835b
Branch: Network-2018-05-01
Copy link
Contributor

Choose a reason for hiding this comment

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

Apologize for missing this, we cannot accept PRs for sdks generated from a branch other than master. If your changes have already been merged in the Network May REST spec, you don't need this PR
Please talk to @MikhailTryakhov if you have any doubts

@dsgouda
Copy link
Contributor

dsgouda commented May 17, 2018

These changes will be introduced with the Network May REST spec sdk

@dsgouda dsgouda closed this May 17, 2018
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.

2 participants