On Dec 24 2010, 6:10 am, Dan Carley <dan.car...@gmail.com> wrote:
[...]
> There are some hack-ish ways to work around it. You can specify that all of
> your includes come from the top scope by prefixing them with ::, such as
> 'include ::mysql'. But this makes for some pretty long winded manifest
> writing if you want to be sure 100% of the time. There isn't
> an equivalent syntax for require meta-parameters. You can achieve
> something vaguely similar with 'require ::mysql' which will create
> dependencies from all resources in the current class. It's certainly not the
> same effect though.
I would expect class name resolution to work the same way everywhere,
so if
notify { "foo':
require => Class["::bar"]
}
does not work then I would account it a bug. If it fails with an
error then fixing it can't break any manifests.
John
--
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.
