Hi Douglas, You do need to be explicit with dependencies between resources; it's a declarative system. You tell puppet what each resource needs, and it does all the work. I've found that it's easy to kid yourself that you've gotten your manifest right, but things only work because dependencies are there from a previous run.
I prefer this to the approach of cfengine, where you had to declare a fixed order for types in an action sequence (files, then exec). Best Julian. 2009/10/24 Douglas Garstang <doug.garst...@gmail.com>: > > All, > > 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. > > 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. > > Or... am I just missing something here? > > Doug > > > > -- Julian Simpson Software Build and Deployment http://www.build-doctor.com --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
