Issue passing parameters

[bmccarty]

Having issues with using parameters in the Powershell pugin. I get the same results if I do a full function in the script panel as my quick little example. Can you let me know what I am doing wrong?

if I setup a param input and try to use the optional parameters, it is getting appended to the command line and breaking somewhere along the way. I've tested this against multiple client machines with the same results.

I made a quick example of what I am seeing.

Here is the output in the console window:

Sending script to agent .....
Script CMD = @powershell -NoProfile -ExecutionPolicy unrestricted -file "%windir%\temp\myPSScript.ps1 -identity administrator"
Executing Script ....Processing -File 'C:\Windows\temp\myPSScript.ps1 -identity administrator' failed because the file does not have a '.ps1' extension. Specify a valid Windows PowerShell script file name, and then try again.

[Cubert]

What version are you on?

Current version is 2.2.6


I believe we fixed that bug already. Looking at my current code base, that command is now generated as such.

Code: Select all

CMD = String.Format("@powershell -NoProfile -ExecutionPolicy unrestricted -file ""{0}"" {1}", myFile, OptPrams)

"MyFile" is now quoted but the optional prams are outside the quotes which should fix the error your seeing.

Let me know if this is on version or not.

[bmccarty]

We are running 2.2.4, I'll check 2.2.6 and post an update if needed. Thank you.

[Cubert]

Ok here is link to downloads

https://delivery.shopifyapps.com/-/31a5 ... afa26b6bb1

[bmccarty]

Works like a charm.
There should probably be some information for formatting the optional parameters field. I noticed if I pass an argument encapsulated in single quotes, that the text is getting sent double encapsulated in single quotes and thus fails. Not really a problem but a a best practice I generally encapsulate my input to the parameter

Note that there is a spelling error in the run page.

[Cubert]

Awesome sauce!