changes to autoload behavior, given new flexible source specification functionality #19
Description
Presently we take a "convention over configuration" approach to configuration autoload that follows a convention of automatically loading a config file name configure.yml in the classpath root. This needs to be updated to support:
- autoloading multiple config files
- autoloading different formats
New convention:
- Any file named "config_._" in the classpath root
- Any file in a any directory called config* in the classpath root
- Do not auto-load the file if the name contains the string "example".
Configuration:
- Sytem environment variable $MILIEU_PREFIX defaults to "config"