Skip to content

Conversation

@henry416
Copy link
Member

@henry416 henry416 commented Jun 7, 2018

Description

Added new VPN protocol from 2018-06-01 REST spec (checked in May 24th)
Azure/azure-rest-api-specs#3133

Checklist

@henry416
Copy link
Member Author

henry416 commented Jun 7, 2018

@markcowl When will SDK be generated for June 15 release?

</None>
<None Include="SessionRecords\Commands.Network.Test.ScenarioTests.VirtualNetworkGatewayTests\TestVirtualNetworkGatewayP2SAndSKU.json">
<CopyToOutputDirectory>PreserveNewest</CopyToOutputDirectory>
</None>
Copy link
Member

Choose a reason for hiding this comment

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

remove all changes to this file

<Reference Include="Microsoft.Azure.Management.Network, Version=19.0.2.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35, processorArchitecture=MSIL">
<HintPath>..\..\..\packages\Microsoft.Azure.Management.Network.19.0.2-preview\lib\net452\Microsoft.Azure.Management.Network.dll</HintPath>
</Reference>
<Reference Include="Microsoft.Rest.ClientRuntime, Version=2.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35, processorArchitecture=MSIL">
Copy link
Member

Choose a reason for hiding this comment

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

remove all these changes

Mandatory = false,
ValueFromPipelineByPropertyName = true,
HelpMessage = "The list of P2S VPN client tunneling protocols")]
[ValidateSet(
Copy link
Member

Choose a reason for hiding this comment

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

Change this from a ValidateSet to an ArgumentCompleter

HelpMessage = "A list of P2S VPN client tunneling protocols")]
[ValidateSet(
MNM.VpnClientProtocol.SSTP,
MNM.VpnClientProtocol.IkeV2)]
Copy link
Member

Choose a reason for hiding this comment

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

Change this from a ValidateSet to an ArgumentCompleter

<package id="AutoMapper" version="6.0.2" targetFramework="net452" />
<package id="Microsoft.Azure.KeyVault.Core" version="1.0.0" targetFramework="net45" />
<package id="Microsoft.Azure.Management.Network" version="19.0.2-preview" targetFramework="net452" />
<package id="Microsoft.Rest.ClientRuntime" version="2.3.11" targetFramework="net452" />
Copy link
Member

Choose a reason for hiding this comment

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

remove all changes to this file

@henry416
Copy link
Member Author

henry416 commented Jun 7, 2018

@markcowl feedback addressed.
Currently uploaded nuget package does not have my change, do we have a date when SDK will be generated for June 15 release? (I checked in REST specs May 24)

@henry416
Copy link
Member Author

henry416 commented Jun 8, 2018

@markcowl Added tests. ArgumentCompleter seems to break powershell inputs, so reverted to original.
Still need to know when June 15 SDK is generated and uploaded, otherwise can't push this.

@markcowl
Copy link
Member

@henry416 marking as 'do not merge' until we hear from the folks managing the network sdk

@henry416
Copy link
Member Author

@markcowl Can we target the June 29th release?

@cormacpayne
Copy link
Member

@praries880 would you mind taking a look at this PR while Mark is OOF?

@cormacpayne
Copy link
Member

@MikhailTryakhov Hey Mikhail, what's the status of this PR?

@praries880
Copy link
Contributor

@cormacpayne We are going to merge the changes into the network branch... heres the PR for that : #6481.

@henry416 / @MikhailTryakhov is it ok to close this PR?

@henry416
Copy link
Member Author

@MikhailTryakhov When will we merge Network-2018-06-01 into build?

@praries880
Copy link
Contributor

@MikhailTryakhov do I need to review this PR? this one was closed in favor of
6481

@MikhailTryakhov
Copy link
Contributor

@praries880 I'm not sure why did @henry416 closed this PR.
He owns his changes delivery so @henry416 please provide more context here

@henry416
Copy link
Member Author

@MikhailTryakhov Didn't you say that by merging changes into 2018-06-01 branch it will eventually go into June 29th release? We already completed the merge for that in the linked PR #6481

@MikhailTryakhov
Copy link
Contributor

@henry416 I will merge all the progress from Network-2018-06-01 to release tomorrow.
To have it delivered you must have all the code you need merged in time to the monthly branch...

@henry416
Copy link
Member Author

Clarified with @MikhailTryakhov offline, this PR can remained closed. Changes were merged to Network-2018-06-01 as intended.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants