Ensure Feature parity between habitat builds and omnibus builds for Chef Client and InSpec packages
Open
Nobody has claimed this yet.
Epic
- Dominant language
- Shell
- Stars
- 35
- Forks
- 35
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 8
Description
In some onsite testing, there was an issue with the version of busybox that chef-client is built with and the way that ohai behaves. This epic is to track the testing work, and other work, necessary to both test the combination of packages that build to become the Chef Client and the InSpec client in Habitat.
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
No files, tests, or entry points are named. Start by mapping the Habitat and omnibus build paths for the Chef Client and InSpec packages, then reproduce the busybox and ohai combination described in the issue. Done means the package combinations have been tested and feature parity has been verified.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100