On Dec 17, 8:34 am, jcbollinger <john.bollin...@stjude.org> wrote: > On Dec 16, 9:17 pm, Alexandre <alexandre.fou...@gmail.com> wrote: > [...] > > > because otherwise Puppet would complain at -parsing- time, not execute > > time, since it does not want to have the same ressource(here service) > > declared twice, even if one is not included for the node, > > Puppet does not exhibit this problem for me. The only way I have been > able to elicit a resource conflict error from Puppet is to have one > node include two classes each declaring a resource of the same type > and name.
I just had an additional thought about this one: are you putting all your declarations into classes? Anything that is outside a class definition is global, so if that file is parsed, such resources (and variables, etc.) apply to all nodes. Incidentally, please do not take this as a cue to attempt to influence global declarations by controlling which files get parsed. You will drive yourself nuts that way. For the most part, you should just put everything into classes. There are some uses for global declarations, but all the ones I can think of have these characteristics: 1) not harmful if applied when unneeded 2) certain to be parsed if needed Resource parameter defaults can sometimes fall into this category, for instance. John -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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.
