Skip to content

Add ResourceGroup to DefaultParameterValues #4911

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 11 commits into from
Nov 15, 2017
Merged

Add ResourceGroup to DefaultParameterValues #4911

merged 11 commits into from
Nov 15, 2017

Conversation

maddieclayton
Copy link
Contributor

@maddieclayton maddieclayton commented Nov 1, 2017

Description

Add default resource group to every cmdlet that has ResourceGroupName mandatory for every parameter #3808. Based off of changes in #4734.


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.

@maddieclayton
Copy link
Contributor Author

@azuresdkci test this please

if ($AddDefaultParameters)
{
$nestedModules = $ModuleMetadata.NestedModules
$AllCmdlets = @()
Copy link
Member

Choose a reason for hiding this comment

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

It feels like we should factor this out into its own function

Copy link
Contributor Author

Choose a reason for hiding this comment

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

done

}

$FilteredCommands = @()
$AllCmdlets | ForEach-Object {
Copy link
Member

Choose a reason for hiding this comment

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

This also feels like it could be in it's own function that returned a predicate, so that this function would basically be

$nestedModules | Get-CmdletType | Where-Object {Test-RequiredParameter -Cmdlet $_ -ParameterName "ResourceGroup"}

Copy link
Contributor Author

Choose a reason for hiding this comment

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

done

{
$rgParameter = $Cmdlet.GetProperties() | Where-Object {$_.Name -eq "ResourceGroupName"}
if ($rgParameter -ne $null) {
$parameterSets = $rgParameter.CustomAttributes | Where-Object {$_.AttributeType.Name -eq "ParameterAttribute"}
Copy link
Member

Choose a reason for hiding this comment

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

I think this variable name is a bit confusing - I thought this was an enumeration of parameter sets, but it is really just anenumeration of parameter attributes. Renaming this to '$parameters' or '$parameterAttributes' would make the code a bit easier to read, I think.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

done

return "`$module = Get-Module $ModuleName `
if (`$module -ne `$null -and `$module.Version.ToString().CompareTo(`"$MinimumVersion`") -lt 0) `
{ `
Write-Warning `"A later version of $ModuleName was found to be imported already. Please see <link> for more details.`" `
Copy link
Member

Choose a reason for hiding this comment

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

I think thsi is a bit out oif date with the latest in Cormac's PR. Please pull the latest

Copy link
Contributor Author

Choose a reason for hiding this comment

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

done

}

else {
return "@()"
Copy link
Member

Choose a reason for hiding this comment

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

Are we return a string representing the code for an array?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yes, when put into the template it will be interpreted as an array.

}
}

function Test-RequiredParameter
Copy link
Member

Choose a reason for hiding this comment

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

Perhaps this should be Test-CmdletRequiredParameter and the parameter name should likely be a parameter.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Done

$FilteredCommands | ForEach-Object {
$global:PSDefaultParameterValues.Add($_,
{
$context = Get-AzureRmContext
Copy link
Member

Choose a reason for hiding this comment

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

What happens if there is no context (the user hasn't logged in yet)? Wnat to make sure that we are not pushing errors into the Error stream.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Added a null check

@markcowl markcowl requested a review from cormacpayne November 6, 2017 16:41
@markcowl markcowl assigned maddieclayton and cormacpayne and unassigned markcowl Nov 6, 2017
@maddieclayton maddieclayton changed the base branch from preview to release-5.0.0 November 6, 2017 23:38
@maddieclayton maddieclayton changed the base branch from release-5.0.0 to preview November 8, 2017 22:59
@markcowl
Copy link
Member

@maddieclayton
Copy link
Contributor Author

@maddieclayton maddieclayton merged commit 9b78152 into Azure:preview Nov 15, 2017
@maddieclayton maddieclayton deleted the DefaultScript branch November 18, 2017 00:49
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.

4 participants