(dsc): `PSResourceList` ignores `scope` when resolving `_exist`
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 72/100
Research direction
Start with ConvertInputToPSResource and GetPSResourceList, then reproduce the two scope cases from the issue using the shown PSResourceList configurations. Trace how omitted and explicit scope values are represented during resource matching and set operations. Done means explicit scope limits _exist, test, and set to that scope while omitted scope preserves the current any-scope behavior.
Written by the indexing model from the issue text.
Description
Prerequisites
- Write a descriptive title.
- Make sure you are able to repro it on the latest released version
- Search the existing issues.
Steps to reproduce
As a user, I want scope to act as a filter when it is specified on a PSResourceList resource entry, so that _exist reflects whether the resource is present in that scope and set only touches that scope.
Today ConvertInputToPSResource defaults scope to CurrentUser when it is omitted, and GetPSResourceList collects installed resources from both scopes and matches on name and version only. The script cannot tell "the user asked for CurrentUser" from "the user said nothing", so scope is ignored when resolving the current state.
Two visible consequences:
-
getreports_exist: truewith a scope that differs from the desired one.resources: - name: PSResourceList scope test type: Microsoft.PowerShell.PSResourceGet/PSResourceList properties: repositoryName: PSGallery resources: - name: Pester version: '5.7.1' scope: CurrentUserWith Pester 5.7.1 installed only in
AllUsers,dsc resource getreturns:{ "name": "Pester", "version": "5.7.1", "scope": "AllUsers", "_exist": true }testthen reports_inDesiredState: falsebecause the scope differs, andsetreinstalls intoCurrentUser. Thegetoutput and thetestresult disagree about whether the resource exists. -
_exist: falsewith an explicit scope removes the resource from a different scope.resources: - name: PSResourceList scope test type: Microsoft.PowerShell.PSResourceGet/PSResourceList properties: repositoryName: PSGallery resources: - name: Pester scope: CurrentUser _exist: falseWith Pester installed only in
AllUsers,dsc resource setrunsUninstall-PSResource -Name Pester -Scope AllUsers. A configuration that only asked aboutCurrentUsermodifies the machine-wide scope and needs elevation to do so.
Expected behavior
When scope is specified, only resources installed in that scope are considered for _exist, test and set. When scope is omitted, the current behaviour (any scope) is kept.
Actual behavior
See the JSON snippet and the Uninstall-PSResource call above.
Error details
Environment data
Directory: C:\Program Files\PowerShell\Modules
ModuleType Version PreRelease Name PSEdition ExportedCommands
---------- ------- ---------- ---- --------- ----------------
Binary 1.3.0 preview1 Microsoft.PowerShell.PSResourceGet Core,Desk {Compress-PSResource, Find-PSResource, …
Binary 1.2.0 preview5 Microsoft.PowerShell.PSResourceGet Core,Desk {Compress-PSResource, Find-PSResource, …
Directory: C:\program files\powershell\7\Modules
ModuleType Version PreRelease Name PSEdition ExportedCommands
---------- ------- ---------- ---- --------- ----------------
Binary 1.2.0 Microsoft.PowerShell.PSResourceGet Core,Desk {Compress-PSResource, Find-PSResource, …
Key : PSVersion
Value : 7.6.6
Name : PSVersion
Key : PSEdition
Value : Core
Name : PSEdition
Key : GitCommitId
Value : 7.6.6
Name : GitCommitId
Key : OS
Value : Microsoft Windows 10.0.26200
Name : OS
Key : Platform
Value : Win32NT
Name : Platform
Key : PSCompatibleVersions
Value : {1.0, 2.0, 3.0, 4.0…}
Name : PSCompatibleVersions
Key : PSRemotingProtocolVersion
Value : 2.4
Name : PSRemotingProtocolVersion
Key : SerializationVersion
Value : 1.1.0.1
Name : SerializationVersion
Key : WSManStackVersion
Value : 3.0
Name : WSManStackVersion
Visuals
No response
- Dominant language
- C#
- Stars
- 576
- Forks
- 114
- Avg merge
- 23h 17m
- Merged PRs (30d)
- 8
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.
More from PowerShell/PSResourceGet
-
Create parent directories only after the containment check in InstallHelper.TryExtractToDirectory Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
PowerShell/PSResourceGet#2056 ·
-
feature_request
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
PowerShell/PSResourceGet#2013 · 3 comments ·
-
feature_request Needs-Triage
PowerShell/PSResourceGet#2057 · 1 assignee ·
-
Needs-Triage
Difficulty 3/5 1-2 days Newbie friendliness 68/100
PowerShell/PSResourceGet#2055 ·
-
(dsc): Export ignores `--input` filter for `Repository` and `PSResourceList` on DSC 3.3.* or above OpenNeeds-Triage
Difficulty 3/5 1-2 days Newbie friendliness 72/100
PowerShell/PSResourceGet#2053 ·
All issues in PowerShell/PSResourceGet
Similar issues
-
type/automation type/tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
t/bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
ci-failure-cause test-failure
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
area:auth FE mvp P3
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
klasolsson81/jobbliggaren#1788 ·