PowerShell / PowerShell/PSResourceGet
[beta10] Main Package should not be installed before dependent packages succeed
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 576
- Forks
- 114
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 7
Description
Steps to Reproduce
Install-PSResource Az.Compute -Verbose- Press ctrl-c to simulate a failure after az.compute has been installed
- Try importing az.compute, it will fail because dependent module
Az.Accountsis not present
Recommended Resolution
Install dependent packages before installing the main package.
Further, why not just use Nuget's already very robust dependency handling and resolution rather than rolling a separate solution for PSGet? This article referenced from MS documentation explains some very good and high performance ways to go about that and I would have expected this module to basically ape this procedure:
https://martinbjorkstrom.com/posts/2018-09-19-revisiting-nuget-client-libraries
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 by reproducing the issue with Install-PSResource Az.Compute -Verbose, interrupting it after installation, and confirming that importing Az.Compute fails without Az.Accounts. Trace the dependency installation and interruption handling, then compare the behavior with the dependency-resolution approach described in the linked NuGet article. Done means dependencies succeed before the main package is installed, or an interrupted install cannot leave it unusable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100