Re: [Puppet Users] variable confusion

2010-08-12 Thread Peter Meier
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > Ugly. If you put your variables in external nodes, you can't easily > set the variable in a parent class and access it in a child class due > to puppet's borked variable scoping. You can put every single variable > at the node level, but having to sp

Re: [Puppet Users] variable confusion

2010-08-11 Thread Douglas Garstang
On Tue, Aug 10, 2010 at 12:48 AM, David Schmitt wrote: > On 8/9/2010 6:23 PM, Christopher Johnston wrote: >> >> Why can't variables be reassigned with a setup like this? >> >> node /.*mydomain.com/ { >>   import mydomain.pp >> } >> >> node /*.yourdomain.com/

Re: [Puppet Users] variable confusion

2010-08-10 Thread David Schmitt
On 8/9/2010 6:23 PM, Christopher Johnston wrote: Why can't variables be reassigned with a setup like this? node /.*mydomain.com/ { import mydomain.pp } node /*.yourdomain.com/ { import yourdomain.pp } In manifest mydomain.pp and yourdomain.

Re: [Puppet Users] variable confusion

2010-08-09 Thread Patrick Mohr
Why not just move everything to a class in a diffierent file? Then put the variables directly in that class? On Mon, Aug 9, 2010 at 9:23 AM, Christopher Johnston wrote: > Why can't variables be reassigned with a setup like this? > > node /.*mydomain.com/ { > import mydomain.pp > } > > node /*.

[Puppet Users] variable confusion

2010-08-09 Thread Christopher Johnston
Why can't variables be reassigned with a setup like this? node /.*mydomain.com/ { import mydomain.pp } node /*.yourdomain.com/ { import yourdomain.pp } In manifest mydomain.pp and yourdomain.pp I have variables that are specific to that site that I want to import only for that site (ie, dns_