I'm almost sure this isn't true could you put just that into a "test.pp" file
and run that in master-less mode to check?
In 0.25.x this would be "puppet --verbose --debug test.pp"
In 2.6.x I think this would be "puppet apply --verbose --debug test.pp"
Note: this is run on the client.
On Mar 10, 2011, at 1:09 PM, Stefan Baryakov wrote:
> Thanks for the response.
> What is the scope of "if myresource exists" part? From what I can tell
> it looks also in modules which are not included for given node.
>
> In my example
>
> Modules:
> class myuser {user {"myuser": homedir => /someplace } }
> class myfile { file {"myfile": owner => "myuser" }}
>
> node mynode { include myfile }
>
> In that case the homedir of myuser on mynode gets changed.
>
> Thanks
> Stefan
>
>
>
>
> On Mar 10, 9:47 pm, Patrick <[email protected]> wrote:
>> On Mar 10, 2011, at 12:42 PM, Stefan Baryakov wrote:
>>
>>> The problem is that if you mention that user in some resource, lets
>>> say file{owner}, the class managing that user gets included form the
>>> auto-require even though it is not included by the external node
>>> classifier.
>>
>> Auto-require won't include a resource. It mostly works like this:
>>
>> autorequre(myresource)
>> if myresource exists
>> require(myresource)
>> end if
>> end autorequire
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected].
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
>
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
