Awesome, that's exactly what I was looking for.
On Mon, Mar 11, 2013 at 11:02 AM, Ellison Marks wrote:
> You don't have access to the configs variable What you do have access to
> is the $title variable, which I think is what you want. This is
> automatically set by puppet to the name of the def
You don't have access to the configs variable What you do have access to is
the $title variable, which I think is what you want. This is automatically
set by puppet to the name of the defined type's instance. In this case,
config1, config2... config100.
http://docs.puppetlabs.com/puppet/latest/
So, this is mostly working now (thanks for the pointers!), but how can I
reference the top level "configs" within my define? For example:
configs:
config1:
Name: app1
WorkingDir: /var/app1
config2:
Name: app2
WorkingDir: /var/app2
...
config100:
Name: app100
Workin
Yes, sorry about the case mixing. That was a mis-paste. Thanks for the
advice, I'll start working through your suggestions.
On Fri, Mar 8, 2013 at 2:49 PM, Ellison Marks wrote:
> Through create_resources, Name and WorkingDir are being passed to your
> defined type as parameters. Your defined t
Through create_resources, Name and WorkingDir are being passed to your
defined type as parameters. Your defined type though, does not accept
parameters. something like this:
define app::virtualApps($Name, $WorkingDir) {
should work, though you'll also have to work out case, as it seems you're
