Issue #2416 has been updated by Luke Kanies. Status changed from Accepted to Needs design decision
Yeah, you're almost guaranteed to result in quite nasty circular dependencies if you do this, and they'll be ridiculous to resolve, and I'll get blamed even though it's your fault. I think the right approach is to find a way to really have resources that we can pin to the beginning or end of a transaction, or at least very close. Does anyone think this feature is really feasible? ---------------------------------------- Feature #2416: Ability to specify Tags in the require/before metaparameters http://projects.reductivelabs.com/issues/2416 Author: Nigel Kersten Status: Needs design decision Priority: Normal Assigned to: Category: transactions Target version: Complexity: Unknown Affected version: 0.25.0 Keywords: I was attempting to clean something up today where we have a large collection of resources that all must be applied 'before' another resource, but not all those resources are necessarily defined for all clients, so we end up needing to scatter 'before' calls all over the place rather than having a central 'require'. It would be awesomely useful if you could do: <code> require => Tag["foo"], </code> and all resources tagged with that tag were required. Same goes for before. I have no idea how feasible this is though. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://reductivelabs.com/redmine/my/account --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en -~----------~----~----~----~------~----~------~--~---
