Jira (PUP-3647) Puppet stores files forever in state.yaml

[Eric Sorenson (JIRA)]

Title: Message Title

Eric Sorenson commented on PUP-3647   Re: Puppet stores files forever in state.yaml Hm, I filed the linked duplicate bug PUP-4460 where it seemed like this is a vestigial file but didn't figure out exactly what the consequences would result from ditching it entirely. Charlie Sharpsteen is this something you could put on your list for cryptoentomological exploration? (If it turns out to actually be necessary, I'm not sure what the right approach would be to solve this problem specifically - seems like we'd need to put some pretty complicated logic in to prune a new state file of resources that used to be managed in (current_catalog - 1) but are no longer in (current_catalog)....) This bit from lib/puppet/resource/catalog.rb appears to be the only usage of the statefile routines.... def apply(options = {}) Puppet::Util::Storage.load if host_config?   transaction = create_transaction(options)   begin transaction.report.as_logging_destination do transaction.evaluate end ensure # Don't try to store state unless we're a host config # too recursive. Puppet::Util::Storage.store if host_config? end   yield transaction if block_given?   transaction end Add Comment   This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.