[scaffolding-chef-infra] Bundle Gems inside the Habitat artifact
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 35
- Forks
- 35
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 8
Description
When running Effortless Config in a Habitat Artifact, the chef-infra client downloads Gems from rubygems.org are still trying to be downloaded and that download fails in an airgapped environment.
One of the benefits of using an Effortless Config is having artifacts which are immutable and easily portable as harts ability to be used in environments that a regular chef-infra client is harder to use in.
Can these cookbook gems be cached when building and then referenced at runtime without the call-out to rubygems.org?
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 locating the Effortless Config and Habitat artifact build flow, then trace how the chef-infra client resolves cookbook Gems at runtime. Verify where the download from rubygems.org occurs in an airgapped run. Done means the required Gems are cached in the hart during the build and runtime no longer calls rubygems.org.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- build-system, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100