Allow to specify custom module path in Install-PSResource

[cmenzi]

Summary of the new feature / enhancement

Install-Module and now also Install-PSResourceGet do not allow to specify the Path where Modules are installed. It only works via Save-Module or Save-PSResource.

It would be great if there is a environment variable or parameter to control where powershell modules are installed when using Scope CurrentUser

Proposed technical implementation details (optional)

No response

[StevenBucher98]

cc @SydneyhSmith since this seems to be a PSResourceGet issue.

[KirillOsenkov]

@SydneyhSmith would it be possible to proritize this? I'm from Azure Data and we have very significant support costs in our org related to modules being in OneDrive. I can also reach out internally if needed.

[o-l-a-v]

@KirillOsenkov

There is also the Save-PSResource -IncludeXml -Path 'your\custom\path' cmdlet, it already does this.

• https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.psresourceget/save-psresource

As long as the path is in PSModulePath Import-Module will work.

[cmenzi]

@o-l-a-v Yes, this is also what I mentioned in the issue. But nobody will remember this all the time.

You usually go to PowerShell Gallery and copy&paste the install-psresource Az and run it. There are also scripts, where somebody ensures that a certain module is installed.

I would really prefer an environment variable or a one-time setting Set-PSDefaultResourceLocation, ..

[o-l-a-v]

@cmenzi

Oops, yep, also mentioned in 1st post.

This is how PowerShell have worked since forever. We've requested the ability to choose path for years. I don't see it happening any time soon. Thus Save-PSResource and set PSModulePath is currently the best workaround IMO.

I'd like PSResourcePath to just use the first path in PSModulePath in user context if choosing CurrentUser as scope (and PSModulePath env variable in system context if scope "Machine").

[cmenzi]

@o-l-a-v

This is how PowerShell have worked since forever.

This module PSResourceGet would have been the chance to change that, isn't it :-). I mean it's something new that could also behave it bit different. I mean every command name has change from Install-Module to Install-PSResource, ...

Why not changing a bit the behavoir or adding one parameter?

[benwa]

This is blocking PowerShell/PowerShell/issues/15552 from moving forward.

For far longer than PowerShell has been around, the localappdata and programdata folders have been the standard way to store application data for user and computers.

Please, make the change so that this can move on.