Issue #2183 has been reported by luke. ---------------------------------------- Refactor #2183: Transactions and catalogs should not clean up after themselves http://projects.reductivelabs.com/issues/2183
Author: luke Status: Accepted Priority: Normal Assigned to: luke Category: agent Target version: 0.25.0 Affected version: 0.24.7 Resources are no longer global in the master branch, and we also do not keep catalogs around for long periods of time, so there's no reason to run the cleanup methods (or even have them) in either the catalog or transaction classes. In addition, they can have significant costs -- removing a resource from a graph means removing each of the edges it's involved in, which can be expensive in a highly connected graph, and it gets even worse if you have many resources to remove. I'm marking this for 0.25, but I'm quite willing to bump it if it's not done by the time the authorization file and rack support done. -- 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 -~----------~----~----~----~------~----~------~--~---
