Hi >> Is this the expected behavior, is there a workaround or is it simply >> a bug? > > I don't think I completely understood your examples, but it's expected > behaviour that Puppet will not manage through recursion any files > you're explicitly managing.
I think you got it. :) > To Puppet, there are implicit and explicit resources; anything that > shows up directly in your catalog is an explicit resource, anything > managed through recursion is implicit. Implicit resources that > conflict with explicit resources always just get ignored. Crucially > for you, when doing recusion, explicit resources cause the recursion > to stop at the explicit point. > > Imagine if you wanted to do recursive management on that second file > statement - what behaviour woould you expect to see, if the top-level > recursion still managed the other directory, especially if purging > were enabled? You'd have the two file statements fighting, it seems. I was also thinking that, but wasn't sure if it really might be the problem. > So yeah, this is expected behaviour, and I don't think it's a bug, but > maybe others disagree. So expected behavior. And I now also see the solution for my use case. I just have to readd, the subsource part. :/ thanks for looking at it and 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 -~----------~----~----~----~------~----~------~--~---
