You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am working on making sure my FA are all on the latest LTS version of dotnet and PowerShell. I'm update my arm template to deploy a PowerShell FA. I set the value of "powerShellVersion": "~7" under the Microsoft.Web/sites/properties/siteconfig
After deploying, I checked the app in Azure and was greeted with this message:
My expectation based on my experience with npm would be that the ~ means "at this version-ish". Do I need to set this specifically to 7.2? If I did, does that mean ~7.2.x?
The text was updated successfully, but these errors were encountered:
Hello @Eonasdan -- "~7" in this case refers to "7.0.x". When we first added support for PowerShell 7.0, this was under the assumption that there would be no breaking changes between Powershell 7.0 and 7.2. Unfortunately, this was not the case, and as a result, we could not directly update customers with ~7 as their PowerShell version to 7.2. Going forward we will require our customers to include both the major and minor version.
Do I need to set this specifically to 7.2? If I did, does that mean ~7.2.x?
Sorry if this is the right place to ask this.
I am working on making sure my FA are all on the latest LTS version of dotnet and PowerShell. I'm update my arm template to deploy a PowerShell FA. I set the value of
"powerShellVersion": "~7"
under theMicrosoft.Web/sites/properties/siteconfig
After deploying, I checked the app in Azure and was greeted with this message:
My expectation based on my experience with npm would be that the
~
means "at this version-ish". Do I need to set this specifically to 7.2? If I did, does that mean~7.2.x
?The text was updated successfully, but these errors were encountered: