PR Summary

What

I'm experimenting with a way to override PSResourceGet install path for modules and scripts, suggested in my comment#1494 (comment).

This PR already got the basic logic working for getting the path override if present! 🥳

Todo

• Maintainers confirm this is something they want, else more work is for nothing.
• Get env variablePSResourceGetInstallPathOverride if present and use it instead of default paths.
• Create cmdletSet-PSResourceInstallPathOverride -Path <path> -Scope <CurrentUser|AllUsers>.
  • Barebone functionality, as in setPSResourceGetInstallPathOverride and add it toPSModulePath if not already there.
  • -WhatIf
  • Check if running as admin and scope is current user?
  • ^ Add "-Force" or "-IgnorePermissionsCheck" switch?
• ? Create cmdletGet-PSResourceGetInstallPathOverride ?
• ? Create cmdletRemove-PSResourceGetInstallPathOverride ?
• Make sureGet-PSResource searches for all paths inPSModulePath
  • Ref.Get-PSResource does not search in user context environment variablePSModulePath #889
• Document changes.
• Create tests.

Related issues / feature requests

• 2018-10-18:Move PowerShell folder on Windows from ${env:USERPROFILE}\OneDrive\Documents\PowerShell to ${env:USERPROFILE}\.powershell PowerShell#8069
• 2021-06-09:Let's move PSModulePath out of the documents folder PowerShell#15552
• 2022-04-07:User context, don't install to%OneDriveCommercial% if OneDrive for Business Known Folder Move (KFM) is enabled #627
• 2023-01-12:Get-PSResource does not search in user context environment variablePSModulePath #889
• 2023-11-16:Allow to specify custom module path in Install-PSResource #1494
• 2024-06-08:Script installation should require less fiddling with PATH #1661

PR Context

PR Checklist

• PR has a meaningful title
  • Use the present tense and imperative mood when describing your changes
• Summarized changes
• Make sure all.h,.cpp,.cs,.ps1 and.psm1 files have the correct copyright header
• This PR is ready to merge and is notWork in Progress.
  • If the PR is work in progress, please add the prefixWIP: or[ WIP ] to the beginning of the title (theWIP bot will keep its status check atPending while the prefix is present) and remove the prefix when the PR is ready.
• Breaking changes
  • None
  • OR
  • Documentation needed
    • Issue filed:
• User-facing changes
  • Not Applicable
  • OR
  • Documentation needed
    • Issue filed:
• Testing - New and feature
  • N/A or can only be tested interactively
  • OR
  • Make sure you've added a new test if existing tests do not effectively test the code changed
• Tooling
  • I have considered the user experience from a tooling perspective and don't believe tooling will be impacted.
  • OR
  • I have considered the user experience from a tooling perspective and enumerated concerns in the summary.