> I don't want to get deeply into the middle of this (and so will > leave my contribution to just this e-mail), but there is > a small point I want to make, that I think Peter touched on, but may > not have gotten across. > > Puppet manifests are declarative, not executable. > > The manifests are not a script which is executed in order, but > rather a declaration of the state in which the client > node should be. Kind of like the difference between Imperative > programming (C/Ruby) and Logical programming (PROLOG). > So you are looking at it saying "I want to evaluate this condition, > then execute this bit of code only if the condition > is true". Puppet wants to look at the state of the node, > compare/contrast to the desired state, then "Make It So". To > do that, you need to know various "Facts" about the node.
I'd like to second that. Thanks for your explanations. cheers pete --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
