Positional Parameter Support

[markcowl]

• Default Behavior
  • For ByName Parameter Set
  • Only Names should be positional parameters, and should occur in reverse order (Name, parent Name, etc.)
  • There should never be more than 4 positional parameters - if a resource has 3 ancestors, it should have no positional parameters in this parameter set.
  • For ByInputObject parameter set
  • InputObject should have position 0
• Configuration Support
  • Should be able to address ‘Position’ as a property of parameter in cmdlet directives
  • Suppress position
  • Set Position Number

[fearthecowboy]

Need configuration to declare this and changes to the cmdlet generator.

[dolauli]

p3

[isra-fel]

@JimMoyle from Desktop Virtualization team is also wanting to support this. We should re-evaluate it. cc @dolauli

[JimMoyle]

From our PowerShell standards docs:

Good cmdlet design recommends that the most-used parameters be declared as positional parameters so that the user does not have to enter the parameter name when the cmdlet is run.

Any parameter called 'Name' is often a good candidate, as are parameters that take in an array rather than single property.

https://learn.microsoft.com/en-gb/powershell/scripting/developer/cmdlet/types-of-cmdlet-parameters?view=powershell-7.3#positional-and-named-parameters

Our docs say, as mentioned above that we shouldn't have more than 4 positional parameters total.