On Tue, May 8, 2012 at 2:59 PM, Daniel Pittman <[email protected]>wrote:
> > The idea is that this simple save function would be behind a REST API > like > > the one you mention. Do the hard work of modeling and capturing data then > > make a call to Hiera#save. If a REST API for Hiera is needed we can build > > one. > > ...but the save function proposed is too abstract from the reality of > data storage to be able to do that. Each backend needs additional > context - or someone to write a custom back-end for their site, ever > time - to be effective. > What additional context is necessary? Why would custom back ends be necessary if the default one we use supports writability? > This is a good idea, but at the wrong level of abstraction. I'm not yet convinced this is the wrong level of abstraction. If I understand your original email, you mentioned building tools that understand the semantics of specific back end storage systems in order to write data into the system. That seems to defeat the whole point of a robust plugin system. If read operations are good enough to warrant abstraction, surely write operations are too. Right? -Jeff -- You received this message because you are subscribed to the Google Groups "Puppet Developers" 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-dev?hl=en.
