Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Disable vagrant-berkshelf plugin by default... #126

Merged
merged 4 commits into from
Dec 31, 2014
Merged

Disable vagrant-berkshelf plugin by default... #126

merged 4 commits into from
Dec 31, 2014

Conversation

tknerr
Copy link
Contributor

@tknerr tknerr commented Dec 31, 2014

...because test-kitchen itself already takes care of resolving the cookbook dependencies via berks.

This is required for situations where a user has vagrant-berkshelf installed. In this case it will automatically kick in if a Berksfile is present. In the best case it would be just double effort, but in can also cause test-kitchen to fail.

In combination with berkshelf/vagrant-berkshelf#248 this will fix the above mentioned issue in test-kitchen/test-kitchen#575

Considerations:

  • it will disable vagrant-berkshelf via the default Vagrantfile.erb
  • for the sake of completeness I added a config option to re-enable vagrant-berkshelf if someone really wants that (even though I can't imagine a good use case for it)
  • added a Vagrant.has_plugin('vagrant-berkshelf') guard so vagrant won't bail out if the plugin is actually not installed

@sethvargo
Copy link
Contributor

I think we should just set it to false, no config option

@tknerr
Copy link
Contributor Author

tknerr commented Dec 31, 2014

Agree, lets not encourage people to work against it :-)

sethvargo added a commit that referenced this pull request Dec 31, 2014
Disable vagrant-berkshelf plugin by default...
@sethvargo sethvargo merged commit 24811d1 into test-kitchen:master Dec 31, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants