This repository was archived by the owner on Jul 14, 2021. It is now read-only.
[SHACK-304] Add Chef Apply as a gem dependency #1631
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
ChefDK holds all the logic for the massive dependency resolution task.
Because of this we have to include Chef Apply as a gem dependency, even
though we only want to expose it via Chef Workstation and not Chef
Apply. That is why we do not appbundle it here but do appbundle it in
Chef Workstation.
As we move the dependency solving logic out of the ChefDK (per
chef-boneyard/chef-rfc#308) and seperate out components
(like policyfile and the 'chef' binary) we will eventually not need this
dependency here. But until that day...
Issues Resolved
SHACK-304
Check List