microsoft / microsoft/winget-cli
`winget configure` to log whether DSC resource unit is actually applied/set or skipped
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 26.4k
- Forks
- 1.8k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 15
Description
Description of the new feature / enhancement
Even though System is in the described configuration state, when performing winget configure, the logging does not indicate if the resources are set or skipped.
For example, with WinGetPackage:
Apply :: WinGetPackage [installGit]
Configuration successfully applied.
even when the package is already installed with the desired version.
It would be great if the logs could indicate whether set was actually called for the unit. Thank you!
Proposed technical implementation details
No response
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 at the winget configure resource-application path and use the WinGetPackage example to trace when a unit is set versus skipped. Done means the configuration log distinguishes an actually applied resource from one already in the desired state and skipped.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100