google-cloud-powershell: Windows installer breaks PSModulePath
I have a number of user-scope modules installed in ~/Documents/WindowsPowerShell/Modules
, which is in the PSModulePath by default. After installing via the windows installer, under user variables, my PSModulePath was set to ;C:\Users\justin\AppData\Local\Google\Cloud SDK\google-cloud-sdk\platform\PowerShell
(note the leading ;
, which looks like a failed attempt to append to the existing path), which caused the default path to not be searched, and my modules to all fail to import. This was a simple fix once I had figured out what was going on, but it took some time to discover.
About this issue
- Original URL
- State: open
- Created 7 years ago
- Comments: 17 (7 by maintainers)
It seems like the issue happens if the PSModulePath for User is empty initially. We are fixing this in the next cloud SDK release.