PowerShell / PowerShell/PSResourceGet
Support for Repository Definition in RequiredModulesFeature Request
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 576
- Forks
- 114
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 7
Description
Summary of the new feature/enhancement
Currently, all modules are assumed to come from a single repository on Install. I would like to be able to define a repository name for any module objects listed in the RequiredModules array of the manifest so PowerShellGet knows where to find them when they are hosted in different places.
Proposed technical implementation details (optional)
RequiredModules = @(
@{ModuleName="MyDependentModule"; ModuleVersion="2.0"; Repository="PrivateRepo"},
@{ModuleName="PublicDependentModule"; ModuleVersion="1.0"; Repository="PSGallery"}
)
Optionally, if I could define just RepositoryUrl and not need to register a repository, that would be another helpful use case.
Duplicate of https://github.com/PowerShell/PowerShellGet/issues/356.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Read the linked duplicate, issue #356, then trace how Install processes RequiredModules in the PSResourceGet repository. Done means module entries can select their own Repository as shown, with the RepositoryUrl alternative clarified or supported; confirm the behavior against the project’s existing test coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, powershell
- Domain
- cli, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 20/100