Skip to content

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

Merged
merged 31 commits into from
Mar 7, 2017

Conversation

jobatzil
Copy link
Contributor

@jobatzil jobatzil commented Mar 6, 2017

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

  • 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.
  • The pull request does not introduce breaking changes (unless a major version change occurs in the assembly and module).

Testing Guidelines

  • Pull request includes test coverage for the included changes.
  • PowerShell scripts used in tests should do any necessary setup as part of the test or suite setup, and should not use hard-coded values for locations or existing resources.

Cmdlet Signature Guidelines

  • New cmdlets that make changes or have side effects should implement ShouldProcess and have SupportShouldProcess=true specified in the cmdlet attribute. You can find more information on ShouldProcess here.
  • Cmdlet specifies OutputType attribute if any output is produced - if the cmdlet produces no output, it should implement a PassThru parameter.

Cmdlet Parameter Guidelines

  • Parameter types should not expose types from the management library - complex parameter types should be defined in the module.
  • Complex parameter types are discouraged - a parameter type should be simple types as often as possible. If complex types are used, they should be shallow and easily creatable from a constructor or another cmdlet.
  • Cmdlet parameter sets should be mutually exclusive - each parameter set must have at least one mandatory parameter not in other parameter sets.

… the temporary fix of the INetworkInterface.ApiVersion
…ls and test recordings for applicationgateway.
…ng related operations. Updated application gateway cmdlets that were not up to date.
@msftclas
Copy link

msftclas commented Mar 6, 2017

@jobatzil,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

@azuresdkci
Copy link

Can one of the admins verify this patch?

@cormacpayne
Copy link
Member

@azuresdkci add to whitelist

@markcowl
Copy link
Member

markcowl commented Mar 6, 2017

@jobatzil You need to remove the app.config from your test project - this is why the build is failing

@jobatzil
Copy link
Contributor Author

jobatzil commented Mar 6, 2017

@markcowl Okay, removed all app.config added by me.

jobatzil added 2 commits March 6, 2017 15:11
…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))]
Copy link
Member

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

Copy link
Contributor Author

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.

Copy link
Contributor Author

@jobatzil jobatzil Mar 7, 2017

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" />
Copy link
Member

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

@markcowl markcowl merged commit 5a342a6 into Azure:dev Mar 7, 2017
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.

5 participants