----- Original Message ----- > From: "jcbollinger" <john.bollin...@stjude.org> > To: puppet-users@googlegroups.com > Sent: Thursday, July 19, 2012 2:06:43 PM > Subject: [Puppet Users] Re: Hiera vs LDAP > > >> And, yes, I know that a hiera back-end could be written to support >> LDAP but that would just be an unnecessary data transference if I'm >> reading it right. > > > I'm not sure what you mean by that, but the advantages of accessing > LDAP via hiera include: > > 1. Abstraction. Module authors don't need to care where data > comes from. > 2. Pluggability. The LDAP back-end could be swapped out for a > different one. That's useful for testing, or for non-LDAP shops > to use the same modules as LDAP shops. > 3. Combining and overriding data. Data packaged with modules or > added / overridden by admins don't need to be recorded in LDAP. > > Depending on how you do your accounting, there may not even be any > more layers in an hiera-based stack. Any way around, getting the > data into puppet means going through a Puppet custom function that > wraps an LDAP client that gets data from your directory.
And as of puppet 3 you will get built in integration of hiera into parameterized classes - without the need for calling any custom functions or assigning local variables. This means all parameterized class written to date will automatically become hiera enabled. And by extension become LDAP enabled if you just wrote an LDAP backend for hiera. The cost of an additional abstraction really just doesnt feature when considering this and Johns excellent points. -- 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.
