Skip to content

Support ResourceGroupNameEquals and ResourceNameEquals as parameters in Find-AzureRmResource #3257

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 4 commits into from
Dec 8, 2016

Conversation

TianoMS
Copy link

@TianoMS TianoMS commented Dec 7, 2016

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 PassThrough 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.
    …in Find-AzureRmResource.

@TianoMS
Copy link
Author

TianoMS commented Dec 7, 2016

/// <param name="resourceGroup">The name of the resource group/</param>
/// <param name="resourceType">The resource type.</param>
/// <param name="resourceName">The resource name.</param>
/// <param name="tagName">The tag name.</param>
/// <param name="tagValue">The tag value.</param>
/// <param name="filter">The filter.</param>
public static string CreateFilter(
Guid[] subscriptionIds,
Copy link
Contributor

Choose a reason for hiding this comment

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

Why are we removing the support for multiple subIds?

Copy link
Author

Choose a reason for hiding this comment

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

we don't have any scenario that has mutiple subsIds in our repo now.

/// </summary>
private bool ResourceGroupNameAvailable()
{
return this.ResourceGroupNameContains != null || this.ResourceGroupNameEquals != null;
Copy link
Contributor

Choose a reason for hiding this comment

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

string.IsNullOrEmpty is better here, no?

Copy link
Author

Choose a reason for hiding this comment

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

Seems we have been doing null check for all parameters. I think we can keep it consistent.

@cormacpayne
Copy link
Member

@TianoMS please update the ChangeLog with changes you have made in this PR under the section Current Release

@cormacpayne
Copy link
Member

cormacpayne commented Dec 7, 2016

@vivsriaus
Copy link
Contributor

LGTM thanks! @markcowl @cormacpayne

@cormacpayne
Copy link
Member

LGTM

@cormacpayne cormacpayne merged commit 951fcee into Azure:dev Dec 8, 2016
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