Zitat von janfrode <janfr...@tanso.net>:
Is there any way to have puppet push an initial configuration file,
and then let local admins modify it without it being overwritten by
subsequent puppet runs ?
have a look at the replace option of the file resource:
http://docs.reductivelabs.com/references/stable/type.html#file
Two examples:
Push-if-not-existing:
-----------------------------
I want to push a default /etc/httpd/conf.d/00-local-defaults.conf ,
but would like to allow the local webmaster to change it if he needs
to override some defaults here.
this one is straightforward using the above parameter.
Push-if-default (maybe based on checksum)
----------------------------------------------------------------
When installing mysql, I want to overwrite the RPM-supplied /etc/
my.cnf with our default, and still let the local mysql-admin to
override the defaults here.
this one might be solved by deploying your default config file
_before_ installing the package, hence rpm will not touch your already
deployed config file and deploy its config file with the .rpmsave
extension. But to detect on a machine with the package already
installed wheter the file should be deployed or not might get tricky.
You could use and exec in front of the file resource to determine
whether the config file have been altered from the one shipped by the
package by using the rpm command, if not, delete it and puppet will
deploy its default for you. However this only works if your default is
not the same as the one shipped with the package.
cheers pete
ps: sorry for the empty mails. I hope to have that flaw finally fixed
in my mailer.
--
You received this message because you are subscribed to the Google Groups "Puppet
Users" group.
To post to this group, send email to puppet-us...@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.
