Aurelien Degremont wrote: > I put /etc/sysconfig/network as an example. AFAIK, unfortunately, > Augeas only handles known files (existing lenses). If we trty to > handle /etc/our_local_config_file, it is not so easy.
Indeed. Really silly design. There was a reason that I wrote "e.g." in my suggestion for Augeas; I often use my own textfile editing types instead. >> Shameless plug: I have a define 'rh_sysconfig' for setting /etc/sysconfig >> entries in a module I've written. You can get it by doing a git clone of >> http://www.nsc.liu.se/~bellman/nsc-puppet-utils.git. It doesn't use Augeas >> for manipulating the file, though, but some custom types for doing even >> lower level editing of text files. > I'm wondering if implementing such low-level define and file edition is > the best Puppet approach? The Puppet:y approach would, imho, be to have resource types on the same level as the builtin resource types 'host', 'mount', 'sshkey', and so on. My 'rh_sysconfig' definition is actually a bit too low-level; better would be a 'sysconfig' definition/type that knows to edit files in /etc/conf.d on Gentoo, /etc/sysconfig on RedHat, and so on, but I haven't gotten around to do that yet. (One problem for these kinds of settings, though, is that they have different names and values on different platforms, so the sysadmins needs to handle that in their manifests anyway.) And of course you would want a 'firewall' or 'iptables' type, types for adding /etc/sudoers entries, types for manipulating Apache configs, and so on, and so on. Whether those types are implemented as builtin types in Puppet, as custom types, or defines built on top of lower-level file editing tools like Augeas and/or my textfile editing types, doesn't matter much. But you very likely want something working on that level of abstraction. Then you can create definitions on top of those for even higher levels of abstraction. However, since the number of config file formats is nearly infinite, we also need to have the tools for sysadmins to write such types or definitions themselves. So we have Augeas, we have my textfile editing types, and we have exec to call out to sed/perl/whatever. And we have the ability to write our own custom types for full power. That's *my* take on it, at least. /Bellman --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
