PowerShell / PowerShell/PSResourceGet

Allow modules to be updated from multiple systems... OneDrive

Open
#1,204 3 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Area-Paths feature_request Needs-Attention :wave:
Dominant language
C#
Stars
576
Forks
114
Avg merge
1d 2h
Merged PRs (30d)
7

Description

Summary of the new feature / enhancement

As a user I want to be able to update modules that are stored in my profile (or a network share) from multiple computers. Many places/companies are migrating to being able to back up my profile to OneDrive, so my modules in stored in c:\Users\{UserName}\Documents\WindowsPowerShell\Modules (for Windows PowerShell) and c:\Users\{UserName}\Documents\PowerShell\Modules (for PowerShell core) and this is great for documents, but not for modules.

If I install a module, let's use the Az module, on PC1 using Install-Module -Name Az I can update the module with no issues on PC1, but let's say I also use a different machine called PC2. On PC2, I have access to these modules because they are in my profile made available via OneDrive, and there is no issue in using them. However, there is an issue when try to run Update-Module Az we get the error "Module 'az' was not installed by using Install-Module, so it can't be updated", but the module was installed using Install-Module, just on PC1.

Proposed technical implementation details (optional)

What I would like to see implemented in Install-Module is the ability to mark this module as being able to update from any location, regardless of where it was originally installed with the Install-Module cmdlet. An example of this might look something like this:

Install-Module -Name Az -Scope CurrentUser -AllowUniversalUpdates
The "AllowUniversalUpdates" would then mark the module as being able to be updated from any machine, as long as the user has write permissions to it. This would also work out to being able to host modules on a network share in addition to just a OneDrive location.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by examining how Install-Module records installation origin and how Update-Module checks that origin. Compare the proposed AllowUniversalUpdates behavior for OneDrive and network-share paths, including write permissions. Done means modules installed on one computer can be updated from another supported location without the current installation-origin error.

Written by the indexing model from the issue text.

Assessment

Tech stack
powershell
Domain
tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.