Passing parameters to nested workflow

Question

If I have the following code, is it possible to pass the collection of parameters passed to New-AutomationVM to the inner Deploy workflow without individually specifying them.

New-AutomationVM is likely to have ~20 parameters, and that is going to be a considerable piece of code to then integrate into a second internal workflow. (that seems vulnerable to errors)

Is there a better way? (I'm sure at some point I've read about all parameters being included in a psobject style variable, but I can't find a reference to it any more)

workflow New-AutomationVM
{
    Param($var1,$var2)
    workflow Pre-DeploymentChecks
    { Write-Output $true }

    workflow Deploy 
    {
        Param($var1,$var2)
        $checkResult = Pre-DeploymentChecks 
    }

    Deploy -var1 $var1 -var2 $var2 
}
New-AutomationVM -var1 "var1" -var2 "var2"

Frode F. · Accepted Answer · 2016-03-29 16:11:02Z

1

Not as far as I know. The usual solution would be Deploy @PSBoundParameters, but neither $PSBoundParameters or splatting are availble in a workflow.

Splatting is not permitted in workflow activities or in calls to workflows.

Source: Technet

All Windows PowerShell automatic variables are valid in workflows, except for the automatic variables in the following list. For a complete list of automatic variables, see about_Automatic_Variables.

•$Args

•$Error

•$MyInvocation

•$PID

•$PSBoundParameters

•$PsCmdlet

•$PSCommandPath

•$PSScriptRoot

•$StackTrace

Source: Technet

edited Mar 29, 2016 at 16:11

answered Mar 28, 2016 at 15:59

Frode F.

55.4k9 gold badges104 silver badges118 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

n01d Over a year ago

$PSBoundParameters does not work within workflows.

Collectives™ on Stack Overflow

Passing parameters to nested workflow

1 Answer 1

1 Comment

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

1 Comment

Your Answer

Sign up or log in

Post as a guest

Related