[Configobj-develop] Multiple layers of config files help

[Pettit, K. (SAIC) <Kei...@bp...>]

I'm working on a app that has multiple levels of configuration.  I'm a =
newbie with configobj so I want to see if there is a better way to do =
this that what I'm thinking of.

The levels of configs I need to have:

Global - I'm using a spec file to set global values
Site - Site level
User - User level options
Project - Project level options
CLI - I'm using optparse right now

With my options it goes top down starting from global, ending at Project =
now until I can figure out how to integrate with optparse.  Here is the =
problem I need to solve with configobj:

* I need the ability to set any of my [key] values as immutable in any =
of the config files from Global to Project.  So I need to give the =
ability in the Global, Site, User, and Project config's to set any of =
the [key] values as immutable, which would means the config's below that =
can't change the value that was just set.

* I need the ability to set whether a list or string in the config can =
be appended or reset by the next config in the line.

* As a end result I need a final config after it has gone through the =
Global, Site, User, Project, options as well as obeyed the rules from =
the two above options I'd like to set.


Any suggestions or help on how to do this would be appreciated.

Thanks,

Keith