Skip to content

New property of the express route resources #4195

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 9 commits into from
Jun 29, 2017
Merged

Conversation

dihan0604
Copy link
Contributor

@dihan0604 dihan0604 commented Jun 26, 2017

Description


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.

Copy link
Contributor

@shahabhijeet shahabhijeet left a comment

Choose a reason for hiding this comment

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

@dihan0604 once SDK is merged, only then this can be sent for PR.

@@ -104,5 +106,11 @@ public class AzureExpressRouteCircuitPeeringConfigBase : NetworkBaseCmdlet
HelpMessage = "RouteFilter")]
[ValidateNotNullOrEmpty]
public PSRouteFilter RouteFilter { get; set; }

[Parameter(
Copy link
Contributor

Choose a reason for hiding this comment

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

@dihan0604 please add tests for this new parameter.

@@ -72,4 +74,10 @@ public override void Execute()
WriteObject(peering);
}
}

public enum LegacyMode
Copy link
Contributor

Choose a reason for hiding this comment

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

Mandatory = false,
ValueFromPipelineByPropertyName = true,
HelpMessage = "The legacy mode of the Peering")]
public LegacyMode LegacyMode { get; set; }
Copy link
Member

Choose a reason for hiding this comment

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

@dihan0604 can you explain the reasoning behind introducing an enum that has True and False values? Why can't we just use a boolean to express this parameter?

@@ -41,7 +41,7 @@ public override void Execute()
this.ExpressRouteCircuit.Peerings.First(
resource =>
string.Equals(resource.Name, this.Name, System.StringComparison.CurrentCultureIgnoreCase));

Copy link
Member

Choose a reason for hiding this comment

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

@dihan0604 revert this change please

@shahabhijeet
Copy link
Contributor

@dihan0604 Did you published required nuget packages that you need for Powershell?

@dihan0604
Copy link
Contributor Author

comment addressed and tests added

@dihan0604
Copy link
Contributor Author

@dihan0604
Copy link
Contributor Author

@cormacpayne cormacpayne merged commit 4f97f10 into Azure:preview Jun 29, 2017
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.

5 participants