Automation of PowerShell Universal Upgrade

Looking into the possibility of automating upgrades to the software. Having a static link to the latest version would make it a bit easier.

For example
https://imsreleases.blob.core.windows.net/universal/production/latest/PowerShellUniversal.latest.msi

What about…

$LatestVersion = Invoke-RestMethod https://imsreleases.blob.core.windows.net/universal/production/v3-version.txt
Invoke-WebRequest "https://imsreleases.blob.core.windows.net/universal/production/$($LatestVersion)/Universal.win7-x64.$($LatestVersion).msi" -OutFile .\Universal.msi
1 Like

Is this wise?

One bug could automatically bring down your environment.

I give my updates at least a week to make sure I have a good working version then, update my version string in DevOps once i’m ready to test or deploy to prod.

I’d be using this for a non-production/test region. And then on a regular bases updating production with a known stable release

1 Like