> Use LDAP, or maybe NIS, to distribute the data. No, seriously, that usually > fits in about point three or four of the usual infrastructure building > checklist, right after getting puppet installed and the manifests in version > control.
In the case of LDAP, how would this work? Would you store your entire puppet config in LDAP or just the user information? I am looking documentation for storing all puppet info in LDAP, and that is a bit unwieldy, since all configuration is stored as key-value pairs. Its almost another language on top of puppet. > Sure: you can use the functions that grab stuff externally, like 'generate', > to do this. That will run a command and process it externally. > > Alternately, a template is erb code run on the *puppetmaster* system, not on > the client. So, that can do anything Ruby can do, including filtering stuff > out rather than adding it in, during the run. > Thanks, will also look into functions and templates. Regards, Rahul -- 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.
