[augeas-devel] Adding new lenses

[Bryan Kearney]

I tend to see both. I envision an appliance configuration tool where new 
  modules are added, each one providing a lens to allow editing of the 
files. I like that alot more then forcing a strict api (change_x, 
change_y) and regex editing.

However, to achieve that I think it would be nice to have lense "types". 
  For example

foo.properties
bar.properties
JarJar.properties

all fllow the same structure. I would love for this to be one lens.
  Or.. three files with an "is_a" relationship to a single grammer.

-- bk


David Lutterkort wrote:
> On Thu, 2008-03-13 at 14:59 -0400, Bryan Kearney wrote:
>> Any way to expose that via the API? I could envision creating a ruby 
>> program which provides a set of lenses.. and setting that dynamically 
>> w/o the need for env variables.
> 
> Yeah, that would be worthwhile; which reminds me; there's really too
> different ways that Augeas can be used: (1) as a standalone tool that
> edits some file based on a custom lens description (2) as a generic
> system service that uses a set of predefined lenses to make most of the
> system's configuration accessible, and in a way that you can rely is the
> same across a big swath of systems.
> 
> So far, I've been more thinking about the second use, though I
> definitely need to work more on making the first a little easier.
> 
> In your scenario, would you want Augeas to just load your lens
> description or would you also be interested in accessing any stock
> descriptions that come with Augeas ?
> 
> David
> 
> 
> _______________________________________________
> augeas-devel mailing list
> augeas-devel at redhat.com
> https://www.redhat.com/mailman/listinfo/augeas-devel