PowerShell / PowerShell/PSResourceGet
Ability to register resource repository without it being used unless explicitly with `-Repository`
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
For testing it'd be great with the ability to Register-PSResourceRepository without it being used by Find-PSResource (and other cmdlets) unless explicitly chosen with -Repository.
Then we can have various test repositorories registered that might not work, but don't break day to day operations with PSResourceGet.
Proposed technical implementation details (optional)
- Add a priority that tells PSResourceGet not to use it by default.
-1?101? - Add an optional parameter switch:
-NonDefault,-Testing? - Add an optional parameter string
-Typethat defaults to'Default'with the option of'Explicit'?
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
Start with the Register-PSResourceRepository and Find-PSResource entry points to understand how registered repositories are selected by default versus with -Repository. Define the repository state or parameter behavior that should support explicit-only repositories, then verify that normal discovery ignores them while explicit selection still uses them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, powershell
- Domain
- cli, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100