complex_args is actually a hashtable where the key is the module option and
the value is the raw value for that option. You might be confusing the
ArrayList with the generic list we use to store variable definitions, that
include complex_args, that are passed to the module_wrapper process.
Cool, that helped a lot. But now into another confusion.
There is an array list getting created which is used to create complex_args
in module_powershell_wrapper and there is a condition in
Parse-Args/GetParam() to use complex_args if $args doesn't have any value.
Since $complex_args variable
Cool, that helped a lot. But now into another confusion.
There is an array list getting created which is used to create complex_args
in module_powershell_wrapper and there is a condition in
Parse-Args/GetParam() to use complex_args if $args doesn't have any value.
Since $complex_args variable
Yep that's correct, the exec_command function doesn't no or care about what
it is executing, it just has the command to run passed in as cmd and option
input data to send over the stdin pipe. It's up to the caller of
exec_command to make sure the command that it wants to run accepts input
data
Awesome, thanks for the brief explanation. So correct me if I'm wrong, func
exec_command is the one which does the pipeliinig execution , which is then
accepted by $input via and then call execwrapper scriptblock ?
On Friday, August 16, 2019 at 2:40:57 AM UTC+5:30, Jordan Borean wrote:
>
> Hi
>
Hi
This particular script is part of the put_file operation for winrm [1]
which is executed like "PowerShell.exe -EncodedCommand ScriptB64".
Part of the put_file method is to read the bytes of the file to transfer
across and send it over the stdin pipe of the process under the WSMan Send
