Just a quick question (whether it really matters or not) about module design.
The following document https://docs.puppetlabs.com/guides/module_guides/bgtm.html Seems to indicate that the sub classes, such as install and service, should inherit the main class so that they have access to the parameters passed into the main class. The main class then simply includes the sub classes install, service, etc. However in checking module in forge, and how I have recently been doing it, the sub classes such as install and service are parameterized as well and the main class simply calls them and passes the parameters pertinent to that class. As an example: class apache ($package_ensure, $service_ensure) { class { 'apache::install': ensure => $package_ensure } class { 'apache::service': ensure => $service_ensure } } The classes apache::install and service don't inherit the main apache class (most best practices seem to indicate not to do inheritance outside of the params pattern). So my question is, what is the best way to do it? Or is it more a matter of preference? Thanks -- 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/f441ca5d-6995-4223-a32b-89ec45747462%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
