Hi,
I have defined a resource like this:
file { "/etc/foo/conf.d" :
ensure => directory,
recurse => true,
purge => true,
force => true,
owner => root,
group => root,
source => "puppet:///modules/foo/client/etc/foo/conf.d",
}
This works fine.
However the directory contains both snippets that need to be taken
verbatim (with mode 644) and executeables that need to be executes and
their output taken (with mode 755). It is ok to deliver the
executeables, since the code running on the target which builds the
actual foo.conf out of the contents of foo/conf.d takes care of this,
but it needs the mode for doing so.
This mechanism is in use inside a Debian package, and I would like to
be of least surprise for the casual user, so I'd like to keep this
scheme albeit puppet would be able to generate a monolithic
configuration itself.
Puppet seems to always reset the access bits for "others", so 644
mutates to 640 on the target system. I cannot say whether this is
deliberate configuration of the people running the puppet master or
whether this is a feature of puppet.
Is this a feature of puppet? If yes, is there a possibility to have
puppet 2.7.18 ship the files with the mode given to them in the
modules/foo/client/etc/foo/conf.d directory on the Master?
Greetings
Marc
--
-----------------------------------------------------------------------------
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Mannheim, Germany | lose things." Winona Ryder | Fon: *49 621 31958061
Nordisch by Nature | How to make an American Quilt | Fax: *49 621 31958062
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
