Avoid depending on system `PATH` for the `chef` top-level wrapper
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 156
- Forks
- 116
- PR merge metrics
- No merged PRs in 30d
Description
Describe the Enhancement:
We don't want our chef top-level wrapper to depend on the system PATH to call the underlying sub-binaries. Perhaps we can hard-code the expected omnibus paths as constants, inject them at build-time, or use a relative path based on the location of this file.
Describe the Need:
The chef command should not depend on the PATH to locate underlying sub-binaries,
that way users can use the CLI out-of-the-box without depending on user customizations.
Current Alternative
Use the PATH. Not desired!
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
Locate the chef top-level wrapper and the code that invokes its underlying sub-binaries. Compare the possible path-resolution approaches described in the issue, then verify that the chef command works without relying on the user's system PATH.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100