> A notify for me says run this resource again, or schedule it to be run > again (it may be scheduled by other classes).
you don't run resources, you manage resources. It is a fundamental concept of puppet that you don't execute a bunch of scripts, instead you describe the state of your infrastructure and let puppet do the necessary steps to fulfill this state. > Why wouldn't I want a resource to be managed multiple times in one run? because you describe the state of your infrastructure with your manifests, hence you describe the state of your resources and this state can't really change various times during the run. What puppet does is a transition of the resource from the current state into the described, expected state and this transition is done at the point when the resource is managed, the point when puppet arrived at the resource while traversing the graph. I agree that you might still say: Well what I'm interested in - and this is what I still describe in my manifests - is the state at the end of a puppet run. However if you think about all the other resources that can receive a notify - especially the exec resource - you end up very quickly finding a lot of more complex situations if a before isn't implied by a notify. cheers pete ps: this is just my point of view how I think that puppet works and I think it's good that it works that way. But it's not the only truth out there... And I'm always open to other ideas. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
