Skip to content
This repository has been archived by the owner on Dec 26, 2017. It is now read-only.

Remove ChefDK dependency in favor of berkshelf gem #324

Closed
wants to merge 1 commit into from

Conversation

spajus
Copy link

@spajus spajus commented Nov 9, 2017

Motivation: not everyone who are trying to run Vagrant with Chef provisioning prefer to have the bulky installation of ChefDK, and berksfile gem simply works.

Judging by the amount of issues complaining about being unable to locate berksfile gem, this is often a problem:
#318
#315

I have doubts about this PR getting merged, as it's an opinionated change, and repo itself is somewhat abandoned, so I am going to maintain a fork with new vagrant plugin, i.e. vagrant-berkshelf-nochefdk if this won't get accepted soon.

Motivation: not everyone who are trying to run Vagrant with Chef
provisioning prefer to have the bulky installation of ChefDK, and
berksfile gem simply works.

Judging by the amount of issues complaining about being unable to locate
berksfile gem, this is often a problem:
berkshelf#318
berkshelf#315
Copy link
Contributor

@thommay thommay left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the PR, but as you say this is an invasive change (and berkshelf is becoming more dependent on Chef, so likely you'll wind up eating an increasing amount of pain going this way) so we won't be taking it.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants