[chef-dev] Re: Re: Re: storing bootstrap templates in the chef server

[Joseph Holsten < >]

That reminds me of gitfs in salt stack:
http://docs.saltstack.com/topics/tutorials/gitfs.html


On 2013-09-12, at 17:16, Josiah Kiehl 
<
 >
 wrote:

> You do want version control, but the same is true of cookbooks as well. I 
> think there's good value in making the templates available on the chef 
> server. In an environment with many engineers, making sure everyone is 
> using the latest template is a hassle. Recently we changed our template and 
> we _still_ get requests asking why they can't bootstrap. "Did you read that 
> email we broadcasted to 
> 
 "
>  "Um... maybe" "Go update your template"
> 
> If templates where stored on the server, versioned properly like cookbooks, 
> Operations or whoever can own the template and put out regular releases 
> that people would be able to use without any overhead of downloading the 
> latest version and putting it in ~/.chef/bootstrap.
> 
> +1 for storing templates on the chef server, provided they're versioned 
> like cookbooks.
> 
> 
> On Thu, Sep 12, 2013 at 8:10 AM, Daniel DeLeo 
> <
 >
>  wrote:
> 
> On Wednesday, September 11, 2013 at 10:05 PM, Joseph Holsten wrote:
> 
>> We've recently had to do some customization of our ubuntu, centos and 
>> windows bootstrap templates. While one of my coworkers was working on one 
>> he asked me, “So how do I upload this to the chef server?”
>> 
>> Does anyone else think it makes sense to store bootstrap templates in a 
>> chef server? Are there any disadvantages I'm not thinking of?
> I think you really want version control and all of the features it provides 
> (history, diffs, etc.) for this sort of thing. So if you're already sharing 
> it via version control, what's the benefit of distributing it by a 
> different mechanism as well?
>  
>> --
>> ~j
> 
> 
> -- 
> Daniel DeLeo
> 
>

Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail