[chef] Re: Re: Consistency for Chef Client installation methods

[anatoly techtonik < >]

I am only trying to start with Chef and I used to installing stuff
from packages. IIRC Chef didn't allow me to see which templates are
available and applicable to my platform. Anyway, the inconsistent
behavior doesn't seem like a bug to me anymore, but an omission from
official docs to explain that installation from package is different
from standard installation.

On Wed, Jul 25, 2012 at 10:48 PM, Jesse Nelson 
<
 >
 wrote:
> If you don't like the default behavior simply make your own template
> and use that.
>
> Templates go into .chef/bootstrap/template.erb  (in your repo or in
> ~/.chef)  use -d name to use your template or use --template-file if
> you want to put them someplace else. Use the the builtin templates
> from chef source as examples:
> https://github.com/opscode/chef/tree/master/chef/lib/chef/knife/bootstrap
>
> IMO the current behavior of default templates (gem install) is what
> people expect. Changing this now would probably cause some people
> serious pain. Especially considering how easy it is to customize to
> your needs.
>
>
> -
> Jesse Nelson
>
> On Mon, Jul 23, 2012 at 1:17 PM, anatoly techtonik 
> <
 >
>  wrote:
>> Hi,
>>
>> After noticing that my `knife bootstrap`ped node doesn't update itself
>> automatically, I've created a ticket to make `knife bootstrap` no
>> different from apt client install, but it was closed as invalid.
>> http://tickets.opscode.com/browse/CHEF-3310
>>
>> I wonder what do people here think about that different methods of
>> Chef Client installation lead to different result? Is it a nice
>> feature or inevitable evil?
>> --
>> anatoly t.