microsoft / microsoft/winget-cli
Configuration does not ensure that required modules are present
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 26.4k
- Forks
- 1.8k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 15
Description
Brief description of your issue
The configuration processor ensures that the target module is present, but it does not ensure that any subsequent required modules are present. This can lead to a situation where the resource module is present, but the module cannot be loaded due to the missing dependencies.
Steps to reproduce
> Install-Module Microsoft.WinGet.DSC
> Uninstall-Module Microsoft.WinGet.Client
> [Apply any configuration using Microsoft.WinGet.DSC]
Expected behavior
Configuration installs any required modules to operate.
Actual behavior
An error like:
The required module 'Microsoft.WinGet.Client' is not loaded. Load the module or remove the module from 'RequiredModules' in the file...
Environment
1.9 era
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 configuration processor and its handling of RequiredModules, then reproduce the issue with Microsoft.WinGet.DSC after uninstalling Microsoft.WinGet.Client. Done means applying a configuration installs or otherwise makes all required modules available, including subsequent dependencies, without the missing-module error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100