(dsc): `Repository` with a local path `uri` is never in desired state
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 3/5
- Tempo stimato
- 1-2 giorni
- Idoneità per principianti
- 68/100
Direzione di ricerca
Reproduce the mismatch with Register-PSResourceRepository -Uri C:\Repo, then run the listed dsc config set and dsc config test commands against the YAML example. Start at the Repository resource's get and desired-state comparison entry points; done means a local path matches its registered file:/// URI, config test reports inDesiredState: true, and a second config set reports no changes.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
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 a Repository instance with a local path as uri to be reported as in desired state once it is registered, so that dsc config set does not re-apply it on every run.
Register-PSResourceRepository -Uri C:\Repo stores the URI as file:///C:/Repo. The Repository resource has no test operation, making DSC compare the get output with the desired properties. C:\Repo never equals file:///C:/Repo, so the instance is never in desired state.
resources:
- name: Local repository
type: Microsoft.PowerShell.PSResourceGet/Repository
properties:
name: LocalRepo
uri: C:\Repo
trusted: true
dsc config set --file .\repo.dsc.yamldsc config test --file .\repo.dsc.yamldsc config set --file .\repo.dsc.yamlagain
Expected behavior
Step 2 reports inDesiredState: true. Step 3 reports no changes.
Actual behavior
Step 2 reports inDesiredState: false with differingProperties: [uri]. Step 3 calls Set-PSResourceRepository again and reports the instance as changed.
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
- Lingua principale
- C#
- Stelle
- 576
- Fork
- 114
- Merge medio
- 1g 2h
- PR unite (30g)
- 7
Guida per i contributori
Apri la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di PowerShell/PSResourceGet
-
Create parent directories only after the containment check in InstallHelper.TryExtractToDirectory Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
PowerShell/PSResourceGet#2056 ·
-
feature_request
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
PowerShell/PSResourceGet#2013 · 3 commenti ·
-
Needs-Triage
Difficoltà 3/5 1-2 giorni Idoneità per principianti 72/100
PowerShell/PSResourceGet#2054 ·
-
(dsc): Export ignores `--input` filter for `Repository` and `PSResourceList` on DSC 3.3.* or above ApertaNeeds-Triage
Difficoltà 3/5 1-2 giorni Idoneità per principianti 72/100
PowerShell/PSResourceGet#2053 ·
-
feature_request Needs-Triage
Difficoltà 4/5 3-5 giorni Idoneità per principianti 64/100
PowerShell/PSResourceGet#2052 ·
Tutte le issue di PowerShell/PSResourceGet
Issue simili
-
bug
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 75/100
sillsdev/languageforge-lexbox#2665 ·
-
bug documentation frontend
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
azurenoops/spin_agent#975 ·
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 86/100
-
:watch: Not Triaged 11.0 fundamentals/subsvc
Difficoltà 2/5 1-3 ore Idoneità per principianti 92/100
dotnet/AspNetCore.Docs#37699 ·
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
SubtitleEdit/subtitleedit#15108 · 1 commento ·