PowerShell Implementation Parameter Mutex example

In a PowerShell function, if you want the parameter to be mutually exclusive, you can use the "Parametersetname" property to define a parameter property in a different parameter or set of parameters.

Many people may not be aware that in the PowerShell function, we can define multiple parameter attributes on the same parameter name, so that matching mandatory allows one parameter to be mandatory in a scene and optional in a different scenario.

?

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 The 25 26

function Test-parameterset {[Cmdletbinding (defaultparametersetname= ' noncredential ')] param ($id, [Parameter ( Parametersetname= ' localonly ', mandatory= $false)] $LocalAction, [Parameter parametersetname= ' credential ', mandatory = $true)] [Parameter (parametersetname= ' noncredential ', mandatory= $false)] $ComputerName, [Parameter ( Parametersetname= ' credential ', mandatory= $false)] $Credential) $PSCmdlet. Parametersetname $PSBoundParameters if ($PS Boundparameters.containskey (' ComputerName ')) {write-warning ' Remote Call '}}

The

function Test-parameterset above will demonstrate that-computername is an optional parameter when the parameter "noncredential" is activated. And when you use the-credential parameter, the-computername becomes the mandatory argument. And when you use the-localaction parameter, both-computername and-credential are optional.