summaryrefslogtreecommitdiff
path: root/spec/lib/puppet_spec/settings.rb
AgeCommit message (Collapse)AuthorFilesLines
2012-09-14(#16189) Make --run_mode a global option and not a settingHenrik Lindberg1-1/+0
In #16189 the problem is described as config print and --configprint disagree. That problem was caused by the option --mode RUNMODE defined in FaceBase not having any effect thus making 'user' be the only runmode available to any Face. Rather than implementing another way of modifying the run_mode (as attempted in FaceBase), this commit makes the previously 'read-only' global setting --run_mode settable from the command line and promotes it from being a setting to a special case around the loading of settings. In order to make this global run_mode the default, the Application class now picks up the default from Settings (where run_mode is handled), and thus the default becomes either the runmode set from the command line, or 'user' which Settings has a fallback (default default). Applications (such as Master) can still set run_mode as part of application initialization - it works as before. Unused/non working code relating to this is removed. Documentation referring to --mode updated.
2012-07-02(maint) Add trailing newlines to all filesJeff McCune1-1/+1
2012-03-27(#13439) refactor spec_helper for spec compatibility between 2.7 andcprice1-11/+4
master
2012-03-22(#7749) doc / tests cleanupcprice1-0/+13
2012-03-20(#7749) Improvements to handling settings, bootstrapping puppetcprice1-0/+10
Major changes include: * support multiple config files (/etc/puppet, ~/.puppet). we no longer use "run_mode" to determine the location of the config file. * remove all references to application run_mode/state from defaults * make the typing of settings a little more strict * create a new setting type for directories, to make us a little less vulnerable to the terrible matching algorithm in FileSetting