3 ms·
I'm having a little trouble taking this article serious when they are talking about ancient versions of Chef, and that being a problem. If you are still on the
by vegardx 11y ago
I'm having a little trouble taking this article serious when they are talking about ancient versions of Chef, and that being a problem. If you are still on the < 0.9 version of Chef you are doing something very wrong. You already have configuration management, it's not really an argument to not update to a somewhat stable release. Chef isn't just a pull-based system, you have things like push-jobs to go the other way around.
ChefDK is amazing. You get all the tools to do things right. Foodcritic will make you write good code, fast. It is hard wired for environments. It has a rigid precedence for anything, that is also well documented. I mean anything.
I work with Ansible, Puppet and Chef, and Ansible is cute, perfect for one-off configurations, but it doesn't do anything chef-solo couldn't do, if you wanted it agentless. Puppet and Chef does more or less the same things, I just find Puppet extremely slow to work with (heira, r10k, different environments, etc), hard to debug and in general just slow.