Not getting expected output when calling PowerShell function from Azure PowerShell Task

Question

Given:

PowerShell 5.1
Azure DevOps Server 2019

I'm trying to call my function directly from my Azure PowerShell Task Arguments, is this possible? I'm not getting any expected output.

param([String] $Name, [Int] $Age, [String] $Path)

Function Foo
{
    Param(
        [String]
        $Name
    ,
        [Int]
        $Age
    ,
        [string]
        $Path
    )
    Process
    {
        write-host "Hello World"
        If ("Tom","Dick","Jane" -NotContains $Name)
        {
            Throw "$($Name) is not a valid name! Please use Tom, Dick, Jane"
        }
        If ($age -lt 21 -OR $age -gt 65)
        {
            Throw "$($age) is not a between 21-65"
        }
        IF (-NOT (Test-Path $Path -PathType ‘Container’))
        {
            Throw "$($Path) is not a valid folder"
        }
        # All parameters are valid so New-stuff"
        write-host "New-Foo"
    }
}

Update 3

Update 2

Update 1

Please add the code as code tags in your question

TorbenIT
– TorbenIT

2022-05-19 13:11:03 +00:00
Commented May 19, 2022 at 13:11 — TorbenIT
– TorbenIT, Commented May 19, 2022 at 13:11
Updated OP with code tags

Rod
– Rod

2022-05-19 13:12:58 +00:00
Commented May 19, 2022 at 13:12 — Rod
– Rod, Commented May 19, 2022 at 13:12

mklement0 · Accepted Answer · 2022-05-20 14:59:35Z

1

If you execute your script directly, it will simply define the Foo function, but never call it.

Place the following after the function definition in your script in order to invoke it with the arguments that the script itself received, using the automatic $args variable via splatting, which allows you to pass arguments via a variable containing an array or hashtable of parameter values, which needs to be referenced with @ rather than $:

Foo @args

The alternative would be not to invoke a script file, but a piece of PowerShell code (in PowerShell CLI terms, this means using the
-Command parameter rather than -File), which would allow you to use ., the dot-sourcing operator to first load the function definition into the caller's scope, which then allows it to be called:

. "$(System.DefaultWorkingDirectory)/_RodneyConsole1Repo/FunctionExample.ps1"
Foo -Name Rodney -Age 21 -Path ""

edited May 20, 2022 at 14:59

answered May 19, 2022 at 13:56

mklement0

452k68 gold badges728 silver badges988 bronze badges

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

10 Comments

Rod Over a year ago

I updated OP with latest results. Not sure what I'm doing wrong?

mklement0 Over a year ago

@Rod, if you pass "Tom", "21", "", you're passing a 3-element array as a single argument; to pass 3 separate arguments (positionally), separate them with whitespace: "Tom" "21" ""

Rod Over a year ago

Please see Update 2 in OP

Rod Over a year ago

you're absolutely correct! Take a look at word Container in OP code. It is surrounded by special quotes, smh. Thanks for sticking with me.

mklement0 Over a year ago

@Rod, splatting is a way of passing arguments that bind to parameters. It doesn't define variables.

|

Collectives™ on Stack Overflow

Not getting expected output when calling PowerShell function from Azure PowerShell Task

Update 3

Update 2

Update 1

1 Answer 1

10 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

Update 3

Update 2

Update 1

1 Answer 1

10 Comments

Your Answer

Sign up or log in

Post as a guest

Related