-
Notifications
You must be signed in to change notification settings - Fork 4k
Multiple Radius Servers for VPN scenario #11550
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
Conversation
@henry416 Please fix the failed tests |
Hi @henry416, changes from |
@msJinLei Can you please review the changes. Specifically the behavior with parametersets (cannot have RadiusServerConfiguration and MultipleRadiusServersConfiguration coexist) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@henry416, Please check "VirtualNetworkGatewayTests.ps1" for the credential scan error.
/azp run |
Azure Pipelines successfully started running 3 pipeline(s). |
@msJinLei Please review |
Yes, we just find signature check doesn't work for a long time. We just fix it recently. |
@msJinLei Fixed |
"Microsoft.Azure.PowerShell.Cmdlets.Network.dll","Microsoft.Azure.Commands.Network.RemoveAzureSecurityPartnerProviderCommand","Remove-AzSecurityPartnerProvider","1","8510","Cmdlet 'Remove-AzSecurityPartnerProvider' has multiple parameter sets, but no defined default parameter set.","Define a default parameter set in the cmdlet attribute." |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please do not suppress the error. You can set a default parameter for "GetAzureSecurityPartnerProviderCommand".
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@msJinLei I'm not suppressing the error for GetAzureSecurityPartnerProviderCommand ? I don't alter that file at all in this PR?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@msJinLei If you are referring to the ShouldProcess line for New-AzRadiusServer, it is because RadiusServer is a sub-object of gateway's VPN server configuration, simply describing a configuration (ip address, score, etc.). There is no need to implement shouldProcess for this subobject especially since running this cmdlet doesn't call Azure.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@msJinLei I'm not suppressing the error for GetAzureSecurityPartnerProviderCommand ? I don't alter that file at all in this PR?
Default parameter set helps user to choose a parameter set when there is a conflict to bind inputs to existing parameter sets. And so this signature error cannot be suppressed.
Even if the issue is not caused by your PR, it does block your PR from merging. That's why I recommend you fix it in your PR.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@msJinLei Ok, but I don't see a "GetAzureSecurityPartnerProviderCommand" error being thrown anywhere? The checks both in this PR and in my local static analysis runs don't show GetAzureSecurityPartnerProviderCommand throwing a static analysis error. The checks are passing all green.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@msJinLei Ok, but I don't see a "GetAzureSecurityPartnerProviderCommand" error being thrown anywhere? The checks both in this PR and in my local static analysis runs don't show GetAzureSecurityPartnerProviderCommand throwing a static analysis error. The checks are passing all green.
You should remove this line.
"Microsoft.Azure.PowerShell.Cmdlets.Network.dll","Microsoft.Azure.Commands.Network.RemoveAzureSecurityPartnerProviderCommand","Remove-AzSecurityPartnerProvider","1","8510","Cmdlet 'Remove-AzSecurityPartnerProvider' has multiple parameter sets, but no defined default parameter set.","Define a default parameter set in the cmdlet attribute."
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@msJinLei Removing that existing static analysis line will cause checks to fail. RemoveAzureSecurityPartnerProviderCommand is owned by a separate team and I do not know the context of which parameter set to make as default for their powershell. Please ask them to change it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@msJinLei Removing that existing static analysis line will cause checks to fail. RemoveAzureSecurityPartnerProviderCommand is owned by a separate team and I do not know the context of which parameter set to make as default for their powershell. Please ask them to change it.
@henry416 We have fixed the issue in the master, please rebase the latest one.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@msJinLei Done.
"Microsoft.Azure.PowerShell.Cmdlets.Network.dll","Microsoft.Azure.Commands.Network.RemoveAzureSecurityPartnerProviderCommand","Remove-AzSecurityPartnerProvider","1","8510","Cmdlet 'Remove-AzSecurityPartnerProvider' has multiple parameter sets, but no defined default parameter set.","Define a default parameter set in the cmdlet attribute." |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@msJinLei Ok, but I don't see a "GetAzureSecurityPartnerProviderCommand" error being thrown anywhere? The checks both in this PR and in my local static analysis runs don't show GetAzureSecurityPartnerProviderCommand throwing a static analysis error. The checks are passing all green.
You should remove this line.
"Microsoft.Azure.PowerShell.Cmdlets.Network.dll","Microsoft.Azure.Commands.Network.RemoveAzureSecurityPartnerProviderCommand","Remove-AzSecurityPartnerProvider","1","8510","Cmdlet 'Remove-AzSecurityPartnerProvider' has multiple parameter sets, but no defined default parameter set.","Define a default parameter set in the cmdlet attribute."
…s per PRcomments" This reverts commit b09407e.
@msJinLei Removing that existing static analysis line will cause checks to fail. RemoveAzureSecurityPartnerProviderCommand is owned by a separate team and I do not know the context of which parameter set to make as default for their powershell. Please ask them to change it. (Git history shows Ishani Gupta as last author) |
"Microsoft.Azure.PowerShell.Cmdlets.Network.dll","Microsoft.Azure.Commands.Network.RemoveAzureSecurityPartnerProviderCommand","Remove-AzSecurityPartnerProvider","1","8510","Cmdlet 'Remove-AzSecurityPartnerProvider' has multiple parameter sets, but no defined default parameter set.","Define a default parameter set in the cmdlet attribute." |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@msJinLei Removing that existing static analysis line will cause checks to fail. RemoveAzureSecurityPartnerProviderCommand is owned by a separate team and I do not know the context of which parameter set to make as default for their powershell. Please ask them to change it.
@henry416 We have fixed the issue in the master, please rebase the latest one.
Description
Add support for multiple radius servers in VPN scenarios (VPN Gateway and vWAN VpnServerConfiguration).
This cmdlet change requires 2020-03-01 network package.
Checklist
CONTRIBUTING.md
ChangeLog.md
file(s) has been updated:ChangeLog.md
file can be found atsrc/{{SERVICE}}/{{SERVICE}}/ChangeLog.md
## Upcoming Release
header -- no new version header should be added