Conversation
- allows us to specify a hash of config variables, comments, and default values - checks the users current configuration - preserves modified settings - restores/updates comments (in case we change something) - adds new variables and removes deprecated ones - saves the user's old config to ~/.openshift/express.bak In response to https://bugzilla.redhat.com/show_bug.cgi?id=816763 Improved handling of debug value from express.conf - Value was always overwritten by command line (or lack thereof) - This may affect other options - TODO: clean this up by parsing command line options into another ParseConfig object for get_var
One more thing - any platform specific issues possible here? Path aggregation? |
There shouldn't be. It uses mostly the same functions we've been using to
|
Just update the one. I'm just being a bit more cautious on changes On Apr 28, 2012, at 3:03 PM, Fotios Lindiakos
|
…or testing and a script to generate that YAML
Think I've gotten everything nailed down. I separated most of the functionality into different functions. Then I wrote tests for all of them trying to cover as many scenarios as I could think of. The tests can be run via rake test (I've also renamed the REST tests so that they don't get run, since they hang unless pointed to an active devenv) |
Will try tonight - thanks for taking and pushing this On Mon, Apr 30, 2012 at 2:37 PM, Fotios Lindiakos <
|
Ended up needing to revert this because of test breaks. The other tests in core are breaking with this changeset. I think you'll need to recreate the pull request with the fixes on top (you may need new changesets as well by creating a patch from the range of changesets). |
https://bugzilla.redhat.com/show_bug.cgi?id=816763
See commit msg for more