CLI for Virtual Network Gateway NAT feature

[gsumit10]

Resource Provider
Microsoft.Network

Description of Feature or Work Requested
Need CLI changes to support NAT feature in VirtualNetworkGateway resource.
VirtualNetworkGateway resource is for the VPN gateway for Hybrid connectivity. We are introducing a new feature to add NAT capabilities to VPN Gateway. Here user can create multiple NAT rules within the gateway and then associate them to VirtualNetworkGatewayConnection.

Minimum API Version Required
2021-02-01

Swagger Link
Azure/azure-rest-api-specs#13481
Azure/azure-rest-api-specs#13734 (minor fix added later)

Target Date
4/31/2021

Please contact Khushboo ( [email protected] ) and me ([email protected]) for any questions on the swagger PR or NAT feature.

[gsumit10]

@Khushboo-Baheti for any comments on swagger/NAT feature

[yonzhan]

network

[msyyc]

@gsumit10 the api-version '2021-02-01' have not been merged into 'master' branch. After the PR merged, we will ask SDK team to release Python SDK. It will take 1-2 weeks. After SDK ready, we need to bump to new SDK for azure-cli. It will take 1~2 weeks. Then it is ok to develop this feature. So it is very hard to catch up with the target date. Could we deliver the feature in S188?

[gsumit10]

Hi, The NRP changes are in 154 so have been published for a long time now. Can we target an earlier api version?

On Wed, Apr 21, 2021 at 7:12 PM msyyc ***@***.***> wrote: @gsumit10 <https://github.com/gsumit10> the api-version '2021-02-01' have not been merged into 'master' branch. After the PR merged, we will ask SDK team to release Python SDK. It will take 1-2 weeks. After SDK ready, we need to bump to new SDK for azure-cli. It will take 1~2 weeks. Then it is ok to develop this feature. So it is very hard to catch up with the target date. Could we deliver the feature in S188? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#17719 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AKDU3NEPSIKZPUAQVZKIUQ3TJ6AYNANCNFSM43AINWFA> .

-- Thanks, Sumit Gupta

[msyyc]

@gsumit10
About 'Can we target an earlier api version?'. What is the meaning of it? Now azure-cli is using '2020-11-01'.

[gsumit10]

@msyyc , can you please share your alias and we can discuss this on teams (or reach out to me @ sumigup on teams)? i understand that sdk is not yet generated but we have done powershell work with private sdk etc to make sure our side changes and validation are done and we are not waiting on sdk release as that has been pending for a couple of months now.

[jsntcy]

@gsumit10, Yuchao's alias is yuchaoyan, you can contact him in Teams.
So you want us to develop CLI using private SDK to validate your changes before public SDK is released?

[gsumit10]

Thanks @jsntcy , Will discuss with Yuchao. Working with a private SDK can help us make progress on the changes. thats what we did with powershell as well. Please let me know if there are any issues.

[gsumit10]

Thanks @msyyc , can you share the timeline for the CLI release

[msyyc]

new azure-cli will be released in about 7 days.