Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Bcfg2/Options/Parser: fix --version option, add test | Alexander Sulfrian | 2014-11-25 | 1 | -2/+9 |
| | |||||
* | Options: gather as much data from config file first | Chris St. Pierre | 2014-11-10 | 1 | -2/+10 |
| | |||||
* | Options: ensure <repository> macros are always fixed up | Chris St. Pierre | 2014-11-10 | 1 | -23/+54 |
| | | | | | | | This fixes several cases in which <repository> macros would not be properly processed: options that are not added to the parser yet when early options are parsed; and config file options whose default value is used. | ||||
* | testsuite: Added unit tests for new option parsing | Chris St. Pierre | 2014-11-10 | 1 | -39/+55 |
| | |||||
* | Add BCFG2_CONFIG_FILE environment variable (regression from 1.3) | Michael Fenn | 2014-04-07 | 1 | -0/+2 |
| | |||||
* | Options: call _set_defaults_from_config before _parse_config_options | Michael Fenn | 2014-03-19 | 1 | -0/+18 |
| | | | | | | | | | | | | | | | | | | | | _set_defaults_from_config must be called before _parse_config_options This is due to a tricky interaction between the two methods: (1) _set_defaults_from_config does what its name implies, it updates the "default" property of each Option based on the value that exists in the config. (2) _parse_config_options will look at each option and set it to the default value that is _currently_ defined. If the option does not exist in the namespace, it will be added. The method carefully avoids overwriting the value of an option that is already defined in the namespace. Thus, if _set_defaults_from_config has not been called yet when _parse_config_options is called, all config file options will get set to their hardcoded defaults. This process defines the options in the namespace and _parse_config_options will never look at them again. | ||||
* | Options: rename _set_defaults to _set_defaults_from_config | Michael Fenn | 2014-03-19 | 1 | -3/+3 |
| | | | | This is to make the method name more in line with what it does | ||||
* | Options: set config file options only for the running parser | Chris St. Pierre | 2014-03-14 | 1 | -5/+4 |
| | |||||
* | Options: Finalize actual value, not default value | Chris St. Pierre | 2014-03-05 | 1 | -2/+1 |
| | | | | This also fixes some extraneous calls in the option parsing loop. | ||||
* | Options: set options debugging with environment variable | Chris St. Pierre | 2014-03-05 | 1 | -2/+24 |
| | |||||
* | Options: Finalize once | Michael Fenn | 2013-12-07 | 1 | -1/+1 |
| | | | | | | | | If finalize is called early, then some options will not be parsed but instead always take the default value (observed with reporting.transport). Calling finalize once at the end of the processing lets all options take the values they were assigned in the config file. | ||||
* | Options: parse config options before setting defaults | Chris St. Pierre | 2013-11-12 | 1 | -0/+1 |
| | |||||
* | Options: made unit test flag public | Chris St. Pierre | 2013-11-12 | 1 | -3/+3 |
| | |||||
* | Options: added workaround for unit tests that use the parser | Chris St. Pierre | 2013-11-12 | 1 | -13/+12 |
| | |||||
* | Options: Don't reparse initial config file | Chris St. Pierre | 2013-10-31 | 1 | -3/+5 |
| | | | | It hasn't been parsed at this stage anyway. | ||||
* | DB: fixed how Django settings are loaded | Chris St. Pierre | 2013-10-30 | 1 | -8/+33 |
| | |||||
* | Options: parse arg list passed in, not sys.argv | Chris St. Pierre | 2013-09-03 | 1 | -1/+1 |
| | |||||
* | Options: fixed error message when bcfg2.conf is not readable | Chris St. Pierre | 2013-08-16 | 1 | -2/+1 |
| | |||||
* | Options: Replace relative imports with absolute | Chris St. Pierre | 2013-08-12 | 1 | -1/+1 |
| | |||||
* | testsuite: fixed most pylint complaints | Chris St. Pierre | 2013-08-09 | 1 | -7/+15 |
| | |||||
* | Options: reparse all arguments on each pass | Chris St. Pierre | 2013-08-09 | 1 | -7/+3 |
| | | | | | | | | | This ensures that required positional arguments are handled properly. If we only reparse the remaining arguments -- i.e., those that were not understood on previous passes -- then we may parse out all of the positional arguments on the first pass, and then on a subsequent pass parse_known_args() will fail because the positional argument is not provided. | ||||
* | Options: fix parsing of ComponentActions and other finalizable actions | Chris St. Pierre | 2013-08-09 | 1 | -4/+4 |
| | |||||
* | Options: wrote completely new option parser | Chris St. Pierre | 2013-06-27 | 1 | -0/+282 |