Situation: systems come from imaging with /var/tree full of (a hierarchy of) stuff that needs to be removed and replaced. I have a 'file/force => true/recurse => true' resource setup to accomplish this.. short and to the point...works great..replaces the folder hierarchy with a new one. Along comes an eager dev who says "I want to split this tree into two types - the difference between these being ~5% of the files." My choices for managing this tree seem to boil down to: 1. Berate the dev. Not v satisfying - like yelling at a puppy. 2. Maintain two (nearly identical - but not quite) file trees. It's all in git so maybe this isn't so bad. Looks messy though. Means having to sync nested trees and keep them straight. 3. Change the tree structure of what's being copied in and don't recurse. Name every sub folder in the 'file' resource according to which node get what. Neater than #2 but lots of extra work. 4. Create a 'merge' solution so I keep the current folder structure and only merge in the changes for the impacted nodes. #1 - lots of unhappiness #2 - seems prone to error #3 - extra work. probably what will happen though. #4 - seems like the most obvious but (AFAIK) it's not supported by puppet. Is there something better? Another choice I've neglected? -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscribe@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/46b4827d-7492-4441-b009-beb7612e5142%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.