[Puppet Users] subscribe => Package

Instead of subscribe => Package, it's require => Package['toola'] or
similar.

If you want to make sure all three packages are installed before the file,
the best thing in this situation is to order the classes.

Either in a separate module altogether or somewhere that makes sense for
you (perhaps the base class of this module), declare the classes in the
order you need:

Class['install'] -> Class['configure']

This will make sure all resources in class install get applied before any
resources in class configure.

The OP does not use 'subscribe'. He uses 'notify', and 'notify' provides a
superset of the behavior of 'before'. With the code he presented, he
should not see Class['configure'] applied before any of Package['toola'],
Package['toolb'], or Package['toolc']. I would like to see a complete,
minimal example that demonstrates the faulty behavior, as I suspect it is
related to something not portrayed in the example given.


What he has written should work just fine. Relationships to classes
sometimes make sense and sometimes do not. Among other things, they do not
make sense for signaling relationships (expressed using 'notify' or
'subscribe', or the ~> or <~ operators).

On the other hand, I don't think signaling relationships involving classes
are any more meaningful than ordinary ones, inasmuch as classes neither
broadcast events nor have a refresh behavior. File resources also have no
refresh behavior, so there is really no point in using 'notify' instead of
'before' in the example. Thus it could indeed work -- for that example --
to set up a relationship at class level. I think there must be more to
this story, though.


John

Actually, if you notify a class or define you will notify every resource contained inside it, causing services to be restarted and refresh only execs to be executed.

My bad. Nevertheless, that's all the more reason why the OP's code ought
to work, if that's all there is to it.


John