Issue #9051 has been updated by Daniel Pittman.
The same branch is updated with the latest version of this code (a forced push, because history has been rewritten during development). This is approaching completion, in that it now has all the code in what looks like the right places, and looking to be doing the right thing. Still broken, though, are some of the collector tests, and by implication the final round of changes are not actually completed yet. Once they are fixed up, and finished, the collection expressions are still way too intimate with the current ActiveRecord schema; the subsequent change will be to abstract that, and ensure that we have portable references to the data we use, not to the database schema it happens to be implemented with. ---------------------------------------- Feature #9051: StoreConfig backend is hard-coded; it should be possible to change to another storage engine. https://projects.puppetlabs.com/issues/9051 Author: Daniel Pittman Status: Accepted Priority: Normal Assignee: Daniel Pittman Category: stored configuration Target version: 2.7.x Affected Puppet version: 0.22.1 Keywords: Branch: https://github.com/daniel-pittman/puppet/commits/feature/2.7.x/9051-storeconfig-backend-should-be-configurable At the moment the StoreConfig backend is hard-coded within Puppet to use an ActiveRecord based database store. It would be great to be able to easily substitute in a new storage engine without having to patch the core, ideally in the same way you can pick another terminus for the `node` indirection to integrate with your ENC. This needs to provide feature parity with the current feature. -- 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://projects.puppetlabs.com/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.
