Doesn't check if powershell.exe is in the PATH
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 13
- Forks
- 55
- Avg merge
- 2d 15h
- Merged PRs (30d)
- 8
Description
Version:
v3.11.2
Environment:
Windows Server 2012R2
Chef Client v4.10.9
Scenario:
Upgrade Chef Infra Client using the chef_client_updater cookbook.
Steps to Reproduce:
Remove everything, but C:\opscode\chef\bin from your system PATH.
Expected Result:
I would expect mixlib-install to throw an exception OR add powershell.exe to the PATH (temporarily, not permanently).
Actual Result:
It returns an array of Mixlib::Install::ArtifactInfo which include things for all OSes.
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 in the mixlib-install code path that resolves or invokes powershell.exe, and reproduce the scenario with only C:\opscode\chef\bin in PATH. Determine whether the implementation should raise an exception or temporarily provide PowerShell in PATH, then verify that returned ArtifactInfo results are limited to the applicable OS.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell, ruby
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100