Config::Loader takes a directory tree of configuration files (in XML, YAML, JSON, INI etc) and merges them into a single hash. It's merge policy allows for the overriding of individual keys locally, to allow easy separation of production and development environments. This merge policy can be customised with regexes or callbacks.
I'm currently trying to register the namespace, and the feedback has been that Config::Loader is not descriptive enough of what the module actually does.
brian.d.foy has suggested Config::Any::Merge. My opinion is below. Do you have any suggestions?