[chef] RE: Re: RE: Re: Re: RE: Re: RE: RE: RE: Re: RE: Re: No chefdk RPM available for RHEL 5?

[Nico Kadel-Garcia < >]

If I use 'berks package', or 'Policyfile', I only get control of cookbooks. 
By using chefdk and locally controlled chef-solo setups, with centralized git 
management, I also get the vital control of node configurations, data bags, 
roles, and if necessary environments. So I'm afraid I don't see any practical 
use for those tools in a small environment, unless I really need to have some 
out of band cookbook deployment method.  I get the equivalent of "Policyfile" 
by doing my Berksfile work in git, working in branches, and pushing changes 
upstream as needed.

Nico Kadel-Garcia
Lead DevOps Engineer

 


> -----Original Message-----
> From: Daniel DeLeo 
> [mailto:
 
>  On Behalf Of Daniel DeLeo


> You’re right about the risk of dynamic updates of code to Chef Servers; 
> that’s
> what the Policyfile feature seeks to address, and I hope you’ll give it a 
> shot as it
> becomes available.
> 
> As for the other parts of your workflow, it seems like this is exactly what 
> `berks
> package` is for.
> 
> 
> --
> Daniel DeLeo