2010/4/3 Jesús M. Navarro <[email protected]> > Hi, list: > > I'm on my first steps using Puppet. Now that the easiest parts are somehow > tamed more and more questions do arise. But let's go one by one. > > For some computers/services we delegate some parts of their administration > (i.e. development environments). I'll take an easy example on the > /etc/hosts > file: > > There should be a '127.0.0.1 localhost' stanza and then one pointing the > host's public IP to its FQDN. But then, the "end user" should have to be > free to add other entries as needed. > > I'm aware that I could go the path of forcing presence on a line by line > fashion but is there any easier procedure for a "do not edit above this > line" > policy so puppet can manage by means of a template part of the file and > then > allow for hand-made modifications on the end part of it? > > TIA. > > You might want to look at http://augeas.net/ It allows you to have specific entries in a file, like /etc/hosts, end users can modify the file as needed but you will have control of those specific entries with puppet+augeas. http://projects.reductivelabs.com/projects/puppet/wiki/Puppet_Augeas
Hope that helps. -- Tony -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
