Lets say I have this for an external node: classes: software::application environment: production parameters: appvar1: appkey1 ... appvarN: appkeyN
The software::application class can access the appvarN variables. I keep seeing people here say stuff like 'oh just move it up into a class'. Well, if I move the parameter definitions out of the node and up into another class like this: classes: software::application software::application_parameters environment: production parameters: then the software::application class CANNOT access the appvarN variables. What made initially think about this is that we are running 10 or more instances of a specific application on a server, and need to set up to 50 variables for each instance. For tidyness, I was hoping that each instance could be split into a separate file and the puppetmaster supported a file include function. Looks like it doesn't. This made me think of simply putting each instance into it's own class, but then of course they go out of scope. Puppet scoping issues strike again! How can I do this? Doug. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
