Am Montag, 7. Dezember 2015 23:59:47 UTC+1 schrieb Dan Mahoney: > > 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? >
Use the roles/profiles pattern. Parametrize httpd and firewall rules from the profile. So httpd and the firewall module are completly separeted. - Thomas http://www.craigdunn.org/2012/05/239/ http://garylarizza.com/blog/2014/02/17/puppet-workflow-part-2/ > 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? > -- 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/1c9c035e-4467-44e9-96ab-ce4cc7074bca%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
