You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 26, 2017. It is now read-only.
Even if the Vagrantfile does not use vagrant-berkshelf, it still runs. We're using Berkshelf to vendor cookbooks, and shipping with the vendored cookbooks so that the end-user does not need ChefDK or Berkshelf installed. If the user happens to have this plugin installed but not ChefDK, the provisioning will fail. I don't really understand why this plugin is auto-enabling itself.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Even if the
Vagrantfile
does not usevagrant-berkshelf
, it still runs. We're using Berkshelf to vendor cookbooks, and shipping with the vendored cookbooks so that the end-user does not need ChefDK or Berkshelf installed. If the user happens to have this plugin installed but not ChefDK, the provisioning will fail. I don't really understand why this plugin is auto-enabling itself.The text was updated successfully, but these errors were encountered: