Install-PSResource doesn't allow for a change in PSModulePath

[russellds]

Prerequisites

• Write a descriptive title.
• Make sure you are able to repro it on the latest released version
• Search the existing issues.

Steps to reproduce

Change PSModulePath using the directions in about_PowerShell_Config PSModulePath.

Create a powershell.cofig.json in Split-Path $PROFILE with the following:

{
    "PSModulePath": "C:\\PowerShell\Modules"
}

Execute: Install-PSResource -Name KeepAlive

Expected behavior

PowerShell module KeepAlive would be installed in C:\PowerShell\Modules.

A solution would be to allow for a PowerShellGet config file, similar to the about_PowerShell_Config, to
set the different paths for PowerShellGet. This would also solve #195 

Actual behavior

Module was installed in `Split-Path $PROFILE`.

Error details

No error returned.

Environment data

ModuleType Version    PreRelease Name                                ExportedCommands
---------- -------    ---------- ----                                ----------------
Binary     3.0.12     beta       PowerShellGet                       {Find-PSResource, Get-PSResource, Get-PSResourceR…

Name                           Value
----                           -----
PSVersion                      7.2.1
PSEdition                      Core
GitCommitId                    7.2.1
OS                             Microsoft Windows 10.0.22000
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
WSManStackVersion              3.0

Visuals

No response

[StevenBucher98]

Thanks for bringing this up @russellds we will look into fixing this.

[StevenBucher98]

@russellds Did Install-Module create the path C:\PowerShell\Modules or was that already created by you?

[russellds]

I created the folder. From browsing the code, it seems like any changes to the $env:PSModulePath are ignored, which makes sense because $env:PSModulePath doesn't identify user paths versus system paths. That is why I think a simple solution would be to have file similar to powershell.config.json as documented in about_PowerShell_Config, something like powershellget.config.json where you could override the value of the user module path for PowerShellGet.

My use case is OneDrive / the Az module. The Az module is so large that it cause issues when trying to update or re-install it with OneDrive conflicts. Being able to override the user modules location would allow me to work around that as well as no longer having to replicate PowerShell modules to OneDrive.

[StevenBucher98]

@russellds I see, there is a way to do this with the Save-PSResource cmdlet. If you do Save-PSResource -Name KeepAlive -IncludeXML -Path <Your path> that should install that module in the designated path. Let us know if this covers your scenario! Thanks!

[russellds]

While a viable workaround, which I am currently using, how does that work with the other functions in PowerShellGet? Both updating and uninstalling a module will require manual tasks.