PowerShell task duplicates the output with Write-Host in the scripts

[dgaharwar]

Headline:
PowerShell task duplicates the output with Write-Host in the scripts

---

Description:
When a result from one PowerShell task is used as input in next, the output/result under History shows duplication. This only happens when using Write-Host cmdlet in the script however with Write-Output we see the expected results.

---

Example/Use case(s):
PowerShell Task 1:

d.pr

Screen Shot on 2023-02-10 at 3-19-10 pm.png

Shared with Droplr

PowerShell Task 2:

d.pr

Screen Shot on 2023-02-10 at 3-19-37 pm.png

Shared with Droplr

Tasks are attached to the Provision phase of a Provisioning workflow.

When executed on instance/server context the result is seen something like this:

d.pr

Screen Shot 2023-02-10 at 3.21.58 pm.png

Shared with Droplr

When the Write-Output cmdlet is use instead, the results are as expected like below:

d.pr

Screen Shot 2023-02-10 at 3.26.27 pm.png

Shared with Droplr

The below article might be useful:

Dotnet Helpers | Enjoy Coding

Difference between write-host and write-output in powershell | Dotnet Helpers

One of the great benefits of PowerShell is its pipeline mechanics that enable the output of one command to be passed to the next command in the pipeline. That output is not sent as basic text but rather the actual objects generated from a command are...

---

[cbunge]

A note, this only impacts when utilizing WinRM and not with the Morpheus Agent or AzureCMD bus. One of the nice benefits of using the Morpheus Agent.