Closed CHDAFNI-MSFT closed 3 years ago
@CHDAFNI-MSFT Were you able to workaround the issue here? You are making a point only about the the parameter naming AllowPreReleaseVersions usage instead of AllowPreRelease?
@CHDAFNI-MSFT Were you able to workaround the issue here? You are making a point only about the the parameter naming AllowPreReleaseVersions usage instead of AllowPreRelease?
@bganapa - Correct I am only making an observation of a typo in the code underneath, "AllowPreReleaseVersions", relating to whatever happens after running that line of code. Unfortunately I don't recall my workaround.....
i just made sure that the module az.bootstrapper is using the AllowPrerelease wherever needed https://github.com/Azure/azurestack-powershell/blob/dev/src/Az.BootStrapper/Module/Az.Bootstrapper.psm1
The typo is likely coming from PowershellGet module itself.
Typo in module incorrectly refers to PowerShellGet's "AllowPreReleaseVersions" when it instead should be "AllowPreRelease"
When running
per instructions on Post deployment configurations for ASDK - error message is received:
PowerShellGet may need to be updated beyond the default OS installed version 1.0.0.1 (latest is currently 2.2.5) in order to support the 'AllowPreRelease' parameter, if true, this should be taken into account for the Install-AzProfile cmdlet.