On Jul 3, 2008, at 2:55 PM, Luke Kanies wrote: <snip> > > The main problem with this is that's it's poor semantics: The name of > the executable isn't inherently the bit-flip to change behaviour, in > that we might have multiple executables that all have the same > assumptions and need the same context. Anyone who's tried to write a > simple ruby script that needed settings from the 'puppetmasterd' > section of puppet.conf have probably wondered why on earth they needed > to set 'Puppet[:name] = puppetmasterd'.
I still can't get this to work either. I have to use the following to get at the values: Puppet.settings.instance_variable_get(:@values)[:puppetmasterd] <snip> > > On a related note, I've recently realized that the settings class > exposes too much information -- 9/10s of the settings are just a means > of not hard-coding information, and they shouldn't actually be exposed > to the user. I think it's time to go through the settings and mark > them specially, so that people aren't forced to look at this huge list > of settings, when they really only ever need to tune a few of them. Maybe an "Advanced Settings" designator vs the normal ones. -Blake --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/puppet-dev?hl=en -~----------~----~----~----~------~----~------~--~---
