PowerShell / PowerShell/PSScriptAnalyzer
AzureRM.* modules held in use by PSSA when Cluster 0.0.0.1 is scanned, prevents uninstall
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 2.2k
- Forks
- 414
- Avg merge
- 13h 1m
- Merged PRs (30d)
- 2
Description
Repro steps
Install-Module -Name Cluster -RequiredVersion 0.0.0.1 -Repository PSGallery
# This depends on AzureRM, which in turn depends on 45 AzureRM.* modules.
# All get downloaded at install.
Invoke-ScriptAnalyzer -Path [PathToCluster] -Recurse -Severity Error
Invoke-ScriptAnalyzer -Path [PathToCluster] -Recurse -CustomerRulePath [someCustomRulesPath]
Uninstall-Module -Name Cluster -RequiredVersion 0.0.0.1
# Succeeds
Uninstall-Module -Name AzureRM.Websites
# One of the dependencies installed.
# Fails to uninstall, says is currently in use.
Expected Behavior
I should be able to uninstall the AzureRM.* modules. I don't expect PSSA to hold on to them.
We are unable to uninstall any of the AzureRM.* modules because something in PSSA is holding on to them. This appears to only happen for the Cluster 0.0.0.1 module.
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
Reproduce the listed Install-Module, Invoke-ScriptAnalyzer, and Uninstall-Module commands with Cluster 0.0.0.1, comparing scans with and without CustomerRulePath. Trace how PSScriptAnalyzer loads modules during these scans and verify that the AzureRM.* modules can be uninstalled afterward; completion means the reported lock no longer occurs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, powershell
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100