-
Notifications
You must be signed in to change notification settings - Fork 4k
Add ConnectionDraining to ApplicationGateway #3582
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
Add ConnectionDraining to ApplicationGateway #3582
Conversation
…ation! (Tests only partial finished)
… the temporary fix of the INetworkInterface.ApiVersion
…o the project file.
…ing cmdlets (it is no resource).
…tionGateway compare function.
…ls and test recordings for applicationgateway.
…6-09-01 to 2016-12-01.
…6-09-01 to 2016-12-01 in Compute part.
…draining cmdlets.
…ng related operations. Updated application gateway cmdlets that were not up to date.
@jobatzil, |
Can one of the admins verify this patch? |
@azuresdkci add to whitelist |
@jobatzil You need to remove the app.config from your test project - this is why the build is failing |
@markcowl Okay, removed all app.config added by me. |
…eIssues.csv since all the changes are on local objects to prevent build from failing.
namespace Microsoft.Azure.Commands.Network | ||
{ | ||
[Cmdlet(VerbsCommon.Get, "AzureRmApplicationGatewayConnectionDraining"), | ||
OutputType(typeof(PSApplicationGatewayConnectionDraining))] |
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.
returns an array of these
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.
It only returns one connection draining object.
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.
I remove the true in write object.
@@ -19,8 +19,8 @@ | |||
<package id="Microsoft.Data.Services.Client" version="5.6.4" targetFramework="net45" /> | |||
<package id="Microsoft.IdentityModel.Clients.ActiveDirectory" version="2.28.3" targetFramework="net45" /> | |||
<package id="Microsoft.Net.Http" version="2.2.28" targetFramework="net45" /> | |||
<package id="Microsoft.Rest.ClientRuntime" version="2.3.4" targetFramework="net45" /> | |||
<package id="Microsoft.Rest.ClientRuntime.Azure" version="3.3.4" targetFramework="net45" /> | |||
<package id="Microsoft.Rest.ClientRuntime" version="2.3.5" targetFramework="net45" /> |
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.
Unfortunately, this change needs to be made across the board, for all modules, changing in one module will just cause conflicts. WIlll discuss how to deal with this change in the mornign before cutting the new branch
…dlet for connection draining and WAF.
Description
Added the support of ConnectionDraining for ApplicationGateways.
Along the AGW specific changes, the Api-Version of the Network part has been changed to 2016-12-01 and thus the test recordings were updated accordingly.
This checklist is used to make sure that common guidelines for a pull request are followed. You can find a more complete discussion of PowerShell cmdlet best practices here.
General Guidelines
Testing Guidelines
Cmdlet Signature Guidelines
ShouldProcess
and haveSupportShouldProcess=true
specified in the cmdlet attribute. You can find more information onShouldProcess
here.OutputType
attribute if any output is produced - if the cmdlet produces no output, it should implement aPassThru
parameter.Cmdlet Parameter Guidelines