> > I started working on the flush part. I have a dev branch (which doesn't > pass all tests just now) at > https://github.com/raphink/augeasproviders/tree/dev/aug_one_handler > > Feel free to test it and let me know if that improves your situation with > the number of files opened by Augeasproviders. >
Awesome, I'll have to check it out! > > 3) Yeah, I definitely know that it depends on the lens. Unfortunately, >> I've just had too many issues over time with lenses missing various >> features *or* being too loose. >> >> > As far as I'm concerned, I consider Augeas to be a parser before anything > else. So I care that my lenses parse as much as possible, and produce valid > files. Nowadays, I'd only make lenses strict if there is a need to strictly > identify parameters and their entry types. > > Fair enough and +1 to this approach. > > >> 4) Unfortunately, I'm referring both to mapping the properties and to the >> Augueas language itself. The learning curve is high on creating new custom >> types and the learning curve is even higher an creating new Augeas lenses. >> Each time I've wanted to create an Augeas lens I ended up frustrated with >> the error handling and ease of testing and just wrote it in Ruby because it >> was faster. I 100% love the idea, I just find it frustrating in reality. >> > > > I understand your frustration. Augeas comes with many lenses already, so > most Augeas providers won't need a new lens. On the positive side, I'm > planning on organizing a full-fledge Augeas course around Puppetconf (4 > days, including Augeas basics, writing facts, functions and providers with > the Augeas ruby lib, as well as writing new lenses). > > Excellent! I hope to be there. Thanks, Trevor -- Trevor Vaughan Vice President, Onyx Point, Inc (410) 541-6699 tvaug...@onyxpoint.com -- This account not approved for unencrypted proprietary information -- -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-dev/CANs%2BFoXgOO1CGmSzx8G%3DV4G%2BAkBT5V%3DaOrs%2Bvr_zOFGFo0%3D4kg%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
