[chef] Re: Re: Re: Re: Template resource: default value for mode attribute?


Chronological Thread 
  • From: Bob Corsaro < >
  • To:
  • Subject: [chef] Re: Re: Re: Re: Template resource: default value for mode attribute?
  • Date: Sun, 5 Jun 2011 09:47:49 -0400
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=hYgHEeILV43AN60326e28GaXiqogFoefzgIP0wsrwmf1heVsuJiLPDkCkUU8dV5JTQ iFMXJqs31c2x9yoX+4lvkUPmi3QgjFrnAGLRyt9Nwyjh/SHJQLxPGLmeKx5rkUvS0kkf yiK0U2THlzRC0heKCUhdarG+3fxHss45YPIBo=

That may be more confusing since many SCMs don't track file mode. Then there are different OSes with different schemes.

Sent from WOPR

On Jun 5, 2011 2:45 AM, "Faiz Kazi" < "> > wrote:
> Ah, I see.
>
> What about suggestion (1), though? I think it might
> be a less of a surprise to users if the effect
> of applying a template resource respected the original
> mode of the file (in the absence of a mode attribute).
>
> If requesting such a change in behavior is not an
> option, it would still be useful for the wiki to
> explicitly mention the umask defaults that apply
> in the absence of a mode.
>
> (I'm happy to do the wiki edit if it's too much of a bother)
>
> Faiz
>
> On Fri, 3 Jun 2011 12:27:16 -0700
> Adam Jacob < "> > wrote:
>
>> This is not always the default - it's going to be a reflection of the
>> user who runs chef's umask. Most operating systems will have this be
>> 0600, but not all of them will - so you can't rely on it as a general
>> rule.
>>
>> Adam
>>
>> On Fri, Jun 3, 2011 at 7:43 AM, Matt Ray < "> > wrote:
>> > I verified this and I've updated the Template entry on the Resources
>> > page to reflect the default.
>> > http://wiki.opscode.com/display/chef/Resources#Resources-Template
>> >
>> > Thanks,
>> > Matt Ray
>> > Senior Technical Evangelist | Opscode Inc.
>> > "> | (512) 731-2218
>> > Twitter, IRC, GitHub: mattray
>> >
>> >
>> >
>> > On Thu, Jun 2, 2011 at 9:34 PM, Faiz Kazi < "> >
>> > wrote:
>> >>
>> >> It appears that if one does not specify a mode,
>> >> files generated/overwritten by template resources
>> >> end up having permissions like -rw------- (0600).
>> >>
>> >> This seems like a sane default. But maybe the
>> >> documentation should make this explicit.
>> >> Right now, the template resource wiki page
>> >> http://wiki.opscode.com/display/chef/Resources#Resources-Template
>> >> reads:
>> >>
>> >> Attribute:      mode
>> >> Description:    "The octal mode of the file - 0755"
>> >> Default Value:  (nothing here)
>> >>
>> >> Take for example the simple case of managing /etc/hosts.
>> >> This file usually has permissions -rw-r--r--.
>> >>
>> >> template '/etc/hosts'
>> >>  source 'hosts.erb'
>> >> end
>> >>
>> >> .. will overwrite /etc/hosts as expected, but if one
>> >> forgets to pass in the mode attribute, '/etc/hosts'
>> >> ends up as readable only by root (i.e., -rw-------).
>> >>
>> >> This is not really a major problem (I simply make sure
>> >> to pass in a mode explicitly).
>> >> but as a suggestion:
>> >>
>> >> (1) For existing files that get 'templated',
>> >> chef-client could just leave the permissions untouched.
>> >>
>> >> OR
>> >>
>> >> (2) Fix the docs to make it very clear that unless
>> >> one specifies a mode explicitly, the file
>> >> created/overwritten by the template will end up
>> >> with the default mode (and that the default
>> >> mode is 0600, not 0755)
>> >>
>> >>
>> >> For the record, I'm still running 0.9.16.
>> >>
>> >> Thanks,
>> >> Faiz
>> >>
>> >>
>> >>
>> >>
>> >
>>
>>
>>



Archive powered by MHonArc 2.6.16.

§