From fc98ab07f3a05cec529e75d53fbd5f234df2a519 Mon Sep 17 00:00:00 2001 From: luke Date: Wed, 15 Mar 2006 16:48:39 +0000 Subject: Fixing #100. I just added a bit of a hack to configuration parsing -- if a group is specified in a section that matches the name of the process, then it is assumed to be the group that the process should run as. The problem is that we are reusing the term "group" here for both the run-group and the file-group. Oh well. git-svn-id: https://reductivelabs.com/svn/puppet/trunk@1036 980ebf18-57e1-0310-9a29-db15c13687c0 --- lib/puppet/config.rb | 8 ++++++++ 1 file changed, 8 insertions(+) (limited to 'lib/puppet') diff --git a/lib/puppet/config.rb b/lib/puppet/config.rb index ff1494ea8..4fb2840b7 100644 --- a/lib/puppet/config.rb +++ b/lib/puppet/config.rb @@ -222,6 +222,14 @@ class Config values[section] = {} end values[section][var.to_s] = value + + # Do some annoying skullduggery here. This is so that + # the group can be set in the config file. The problem + # is that we're using the word 'group' twice, which is + # confusing. + if var == :group and section == Puppet.name and @config.include?(:group) + @config[:group].value = value + end next end -- cgit