Re: [Puppet Users] Overriding resources created with a define

2010-01-08 Thread Trevor Vaughan
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I think that the issue is that the define isn't actually scoped under the class, so the inherit doesn't pick up that the file is actually under that class at all. Does that make sense? Try writing the same statement but move the defines outside of th

Re: [Puppet Users] Overriding resources created with a define

2010-01-08 Thread John T. Guthrie
Hello all, First, I would like to thank you for your suggestion about an 'if/case' statement. I think that should do what I want. However, I would think that even if defines are scoped separately from classes, that wouldn't necessarily apply in the case that I outlined below since I used a

Re: [Puppet Users] Overriding resources created with a define

2010-01-08 Thread Trevor Vaughan
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 So, I believe (someone please correct me if I'm wrong) that defines are actually separately scoped from the classes that contain them and cannot currently be overridden. The nesting that you have below is merely a convenience for writing: define test

[Puppet Users] Overriding resources created with a define

2010-01-08 Thread John T. Guthrie
Hello all, Suppose you have a resource that is created with a define such as the following: class test { define myfile () { file { "/tmp/$name": content => generate("/bin/echo","$name"); } } myfile { "foo": } } And it turns