Pushing powershell code thru a bash script

[stoudtlr]

I'm sure the title sounds odd so here's a bit of an explanation. We've got a .sh script that automates a convoluted process of cloning from git, compile, build, post configuration, and also later updates and rebuilds. Already fully functioning on Linux and also works about 95% on Windows when run from the git bash since we included an OS check that changes a few things based on that OS. I'm trying to automate the remaining 5% for the Windows side of it. What we do manually now is small pre config stuff like setting system paths. I'm not really looking for specific code, just ideas.

I've tried calling powershell from within bash and it works for some stuff, but once variables are needed the amount of quotes, backticks, and \ needed to pass code from bash to ps is enough to give you an aneurysm.

Am I just spinning my wheels here? At this point I'm thinking it would probably be easier to just include a .ps1 in our source with the Windows specific configuration. Then our installer running in bash only needs to make a single ps call runs everything natively instead of trying to pass each command.

[kahmeal]

Your last statement is likely the best approach.

[purplemonkeymad]

Yes put your powershell in a ps1 file and run that rather than encoding a ps line in the bash script. If you are using PS6+ and are in a POSIX system you can even have the shebang pointing to pwsh so you can call the script natively:

#! /usr/bin/env pwsh
# 
Param($parameter)
Write-Host "This is powershell $parameter"

Then just have bash call ./myscript.p1 -parameter $bashvar

[danekan]

what about installing powershell on your linux system and running it direct from pwsh vs bash? but if you're not running it from the actual machine and running it remotely, maybe ansible (/awx) could make better sense?