[Puppet Users] Re: variable usage in a string, scenario dependent?

2012-09-22 Thread Zachary Alex Stern
It turns out that you do always need the {}, and this just works because the / in the path breaks the variable-finding regex. Thanks to rodjek on irc! :-D On Saturday, September 22, 2012 3:15:07 PM UTC-4, Zachary Alex Stern wrote: Possibly stupid question - how do I know when I have to use

Re: [Puppet Users] variable scoping?

2012-08-14 Thread Zachary Alex Stern
Sorry typo: class puppet ( $server = $puppet::params::server ) inherits puppet::params { FWIW, this works: class puppet::config { include puppet::params $puppetserver=$puppet::params::puppetserver $runinterval=$puppet::params::runinterval file { '/etc/puppet/puppet.conf':

Re: [Puppet Users] variable scoping?

2012-08-12 Thread Zachary Alex Stern
So, your explanation makes sense to me - but that doesn't exactly explain to me why the include statement isn't enough. E.g. when I'm including the puppet::params class in the puppet::config class, what affect is it having at all, if not setting things like the variables included in the

Re: [Puppet Users] variable scoping?

2012-08-11 Thread Zachary Alex Stern
Sorry, that should be $puppetserver = $puppet::params::puppetserver -Eric Seems like at that point I may as well just do this inside the template: %= scope.lookupvar('puppet::params::puppetserver') % -- You received this message because you are subscribed to the Google Groups

Re: [Puppet Users] variable scoping?

2012-08-11 Thread Zachary Alex Stern
Also, fwiw, I've read that document on scoping beginning to end several times. Doesn't mean much to me I'm afraid - pretty new to all this. On Saturday, August 11, 2012 10:36:48 PM UTC-4, Eric Shamow wrote: The best reference to explain how variable scoping works in Puppet is this one -