I'm this case you should (must) have two separate installs, one chef-dk for developing cookbooks, etc. And one chef-client alone toanage the node as Amy other node.
This mean having a knife.rb with your user cert and a client.rb with your workstation key.
Chef-client ithin chef-dk is not supposed to manage a node (even if it can)
Main principle, have a tool for each purpose, never mix or you'll hit a breaking change somewhere ;)
My thoughts, just supported by own experience with various tooling with no factual evidence to present. Given As Is ;)
I get that, but I actually use it to manage my workstation!On Wed, Jun 24, 2015 at 4:39 PM, Noah Kantrowitz <noah@coderanger.net> wrote:
On Jun 24, 2015, at 1:34 PM, Fabien Delpierre <fabien.delpierre@gmail.com> wrote:
> Hello,
> Thanks for the heads-up.
> So this is probably going to sound stupid, but how do I install it? Running OS X 10.10.3 with ChefDK 0.6.0 or 0.6.1 (I don't think I installed 0.6.2 yet).
> I tried installing it but I'm a bit mystified by what's going on: http://pastebin.com/TGBrMDgs
> If you can share any ideas to get it to work, I'd appreciate it :) Meanwhile I'll go install ChefDK 0.6.2, I've been meaning to, so I might as well.
This is something you would install on your servers, not your workstation. New ChefDK packages with the new Chef version will appear eventually, but that will be a separate release.
--Noah
Archive powered by MHonArc 2.6.16.