On 6/10/15 1:03 PM, Albert Shih wrote:
Hi,I would like to known if it's possible to extend a module without touching the module. I mean let's take sample : If I want use apache (from puppetlabs) but each time I create a vhost with apache::vhost { 'thing' : } i want also add a nagios check on my nagios server. For that I can : Change a small amount of code inside the module apache. --> not very complicated but each time they are a update I need to redo the modification. Create my own module who just call the official apache module. But that's suck too because they are ton of parameter. Of course I don't need all of them, but with time this module going to grow. And I get same problem with update. So are they some technics to do that ? In other way how you do that ? Regards -- Albert Shih Heure local/Local time: mer 10 jui 2015 21:55:53 CEST
IMO it's best to deal with local methodology in a profile class that wraps your model. I've written a few pages about how I approach the problem as well a short presentation. Should give you a few ideas about how to approach it.
https://ask.puppetlabs.com/question/5235/what-goes-in-the-profile-part-of-roleprofile/ https://github.com/rkhatibi/sipmug-feb2015 Ramin -- 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 puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/5578C018.8010609%40badapple.net. For more options, visit https://groups.google.com/d/optout.
