On 3 May 2012 23:32, jcbollinger <john.bollin...@stjude.org> wrote:
>
> Hmm. I guess I misunderstood your objective. It is still true that
> 'defined' is not a good approach, however, and also that
> os::motd::register is a bit rude to not take care of declaring its
> dependencies itself.
>
> It might work to declare all your os::motd::register instances
> virtually, right where they now are, and then collect them at the end
> of each node definition. I suspect, though, that you would end up
> with the same problem you already have.
>
> Generally, I recommend replacing "is foo defined?" conditions with "is
> foo *supposed to be* defined?". The latter can be evaluated based on
> global or class variables, or (better) external data.
It's a fine use case for virtual resources. Each class would declare the
virtual:
class pulp {
@os::motd::register { $name: }
...
}
Then os::motd would, when included in the catalog, collect/realize
everything available:
class os::motd {
Os::Motd::Register <| |>
...
}
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@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.
