New parameter for chef omnibus installer to support ChefDK

[sylus]

Chef recently added some endpoints and a -P chefdk option to install.sh for their upcoming chefdk release.

Was wondering if this something that could be taken into account here?

[lucaspottersky]

Now that they have release ChefDK, is there a way to make the vagrant-omnibus plugin install it? I'm trying to use the vagrant-berkshelf plugin, but it requires ChefDK >= 0.2.0.

[tmatilai]

This plugin installs the Chef client on the guest, while ChefDK is a toolkit for your workstation, so IMHO it is out of scope for vagrant-omnibus.

[sethvargo]

👍 to what @tmatilai said.

[stanlemon]

@tmatilai When using vagrant chef-solo having ChefDK on the instance is hugely helpful, especially if one is responsible for prepping vagrant and corresponding configs for a team.

[johnbellone]

@tmatilai @sethvargo I'm going to have to disagree here. This would be very useful for bootstrapping an OpenStack instance that one wishes to use for cookbook development. Without this we're going to need to have a separate installation for Chef as well as Chef DK.

Please reconsider.

[vinyar]

bump.
I see more and more people using Vagrant box as their primary workstation for cookbook development. Which leads to a bit of chefception - omnibus plugin to install chef, chef-client to install chefdk.

It would be fantastic if there was a switch to install chefdk via the omnibus plugin, especially since the script now supports chefdk (including rc builds)
curl -L https://chef.io/chef/install.sh | sudo bash -s -- -P chefdk -p

[sethvargo]

Vagrant 1.7+ installs Chef automatically on everything but windows (coming soon).