Powershell start process using call operator and passing custom credentials - powershell

Question

I'm trying to execute DbUp application using Octopus deployment.
Instruction says to use this simple script:
& .\DbUp.exe | Write-Host
But the problem with that is I couldn't find the way to pass custom credentials to process start. I tried to use Process object directly:
"DbUp Deployment Script starting." | Write-Host
$pinfo.Username = $OctopusParameters['serviceCustomAccountName']
$pinfo.Domain = "DOMAIN"
$pinfo.Password = (ConvertTo-SecureString -String $OctopusParameters['serviceCustomAccountPassword'] -AsPlainText -Force)
$pinfo.FileName = "C:\DbUp.exe"
$pinfo.RedirectStandardError = $true
$pinfo.RedirectStandardOutput = $true
$pinfo.UseShellExecute = $false
$pinfo.Arguments = ""
$p = New-Object System.Diagnostics.Process
$p.StartInfo = $pinfo
$p.Start()
$p.WaitForExit()
$p.StandardOutput.ReadToEnd() | Write-Host
$p.StandardError.ReadToEnd() | Write-Host
"DbUp Deployment Script finished." | Write-Host
But this approach results with no StandardOutput being passed to Octopus log:
DbUp Deployment Script starting.
True
DbUp Deployment Script finished.
It seems to not execute the DbUp.exe at all because no changes are applied to database.
Is there a way to start process using call operator (& .\DbUp.exe) and passing custom credentials? If not, what might be the reason for Octopus not picking output form console app?

Answer 1

The powershell user context is associated with the user running the tentacle service, so that service can be admin and have db connection rights. The -NoNewWindow flag used with start-process should re-direct output to the same session.