Hi, your approach is not all that bad. You might want to consider adopting Roles and Profiles.
Your "wrapper" class is essentially a role. The relationship Class['::local_repository'] -> Class['::spacewalk'] is probably the way to go, assuming that your modules have sound internal relations (through the Anchor Pattern or contained classes, most likely). As for the additional profiles you need, you can make them depend on the spacewalk module with the same syntax. HTH, Felix On 10/31/2014 11:25 PM, Royee Tager wrote: > Hello all, > > I really need your assistance as I'm lost. > My scenario is as follows: > > 1. I wrote two Puppet modules: local_repositroy & spacewalk (attached) > 2. I use Foreman as ENC > 3. I override the class parameters of the 2 Puppet modules with the > smart class parameter option of the Foreman > 4. The local_repository module configures a local repositroy which holds > the RPMs for the spacewalk installation so it has to run before the > spacewalk module > 5. I have other modules which install other RPMs so those modules have > to run only after the spacewalk module so the order should be as follows: > local_repositroy -> spacewalk -> module A > local_repositroy -> spacewalk -> module B > local_repositroy -> spacewalk -> module c > ...... > ...... > 6. How do I tie it all together? I have been told, that I might need to > write some kind of a wrapper but I'm not sure / know how to do it. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/54607DBF.9000209%40alumni.tu-berlin.de. For more options, visit https://groups.google.com/d/optout.
