Hey all, Everything I've done thusfar in creating my own custom modules has drilled some basics into my head -- these are right from the puppet web docs:
"A module’s classes, defined types, and plugins *should all be related,* and the module should aim to be *as self-contained as possible.* Manifests in one module should never reference files or templates stored in another module." I've also seen it preached hard that modules should attempt in all cases to be "portable". So, with that said -- how is the best way to declare dependencies across modules? For example, I have a one-file-per-rule firewall stack, where rules are placed in /etc/firewall.d, and loaded using a standardized ordering script -- this way my "httpd" module can add (and own) an "httpd" firewall rule. How would I tell my web module that if that firewall type is in play, that it should add a file there, and reload the firewall? How do I get the web module to only do this *if* that firewall type is in play, without directly *requiring* it? I have a similar thing for syslog, where I can populate a directory and have individual packages own files in there. Same question. I also have a similar thing for logfile rotation. Same question. I don't want to build huge metaclasses all in site.pp -- nor does it seem sane to me to build meta-modules that do all the combining, although those *are* both ways forward. Thanks, -Dan -- 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/6e51be82-b270-4cb8-bf31-90e39eedd9cc%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
