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 in
Hi out there,
Is there a good way to avoid auto-requiring of resources that are in
modules, which are not included for a given node?
Here is an example - there is a definition of a user, lets say a
service service account, which is present on all nodes for given
environment and some property of t
