On Sat, Oct 24, 2009 at 12:42 AM, Douglas Garstang <doug.garst...@gmail.com> wrote: > I've been putting a lot of puppet pieces together over the last few > days, and I've realised, I think, that you _REALLY_ need to be > explicit with your object dependancies. It looks like puppet just > drags all modules, all nodes, and everything else into one giant > namespace and executes them in NO PARTICULAR ORDER on the target.
That is correct, and while it may seem counter-intuitive, this is really a feature. > I see examples on the puppet recipies page that probably won't work > most of the time since puppet executes things in an apparently random > order. For example, the LDAP example at > http://reductivelabs.com/trac/puppet/wiki/Recipes/LDAPClientNSSwitch > makes no mention of the fact that the ldap.conf file needs to be > updated BEFORE the service is started by putting a before=> on the > file, or a require=> on the package. What service? That manifest doesn't declare any service resources. > Or... am I just missing something here? Many Puppet newcomers are startled by this behavior. Some were so startled they went off to join another project. Over time, I've learned to love this behavior, it means my manifests a) *fully* document the setup of a particular configuration and b) Always work, even if someone refactors things and reorders the declarations in the file. This is very important in a setting where multiple sysadmins are working on the same manifests. Regards, Paul --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
