On Jun 15, 2012, at 3:25 PM, Ashley Penney wrote: > I figure I should clarify a little bit. Unless my understanding of Puppet > internals is way off it would be quite a lot of work to add the filter as it > stands. A lot of code would have to change internally to make it capable of > filtering on parameters. By complexity I meant code wise, not puppet > manifest/syntax wise. I just meant that it would take a lot of development > to get it working consistently and properly as a metaparam throughout the > codebase. It would be nice to hear from someone at puppetlabs just how > difficult this would be to add based on the 3.0 codebase.
I've looked at the code. It requires changing the triggers to have attributes, which is honestly a fairly trivial change and likely backwards compatible with anything today, too. Look at Puppet::Relationship.match? () -- it's accepts the idea of event types, but only has triggers for :ALL_EVENTS or :NONE. That or else could be replaced with specific event types being passed quite easily. Then each object would have to be modified to accept a revised syntax in the situation (optional) where only specific types are desired. It really doesn't appear to be a large change. -- Jo Rhett Net Consonance : net philanthropy to improve open source and internet projects. -- 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.
