On Tuesday, June 9, 2020 at 6:22:55 AM UTC-6, A Manzer wrote: > > Option A, 100%. > > Why change your coding pattern just because a module isn't from the > Forge? Who knows, maybe one day you'll post it yourself on the Forge! >
I try to write modules as if I am going to post them to the Forge. So I guess that alone should have been my answer. > Sometimes I do the full parameter workup like in your example, and > sometimes I just use `include` and let Hiera fill in the parameters, > without having to add 'profile::' at the beginning of every parameter. > > I've done the same thing in the past, just use Hiera to provide params to technology modules. It feels a little off, it seems like the "right" way is to wrap a technology module in a profile and then put the profile:: params in Hiera. > > You seem to be making things more complicated by using `contains` and > those Refresh arrows though. Why not just use `include`? > Honestly I was just putting a few w things in my example class to flesh it out but I used contain because I use the Puppetlabs NTP module <https://github.com/puppetlabs/puppetlabs-ntp/blob/d6a91973674cd003e6558ba0e1da16a6f1ab444d/manifests/init.pp#L309> as my template or benchmark. The subtleties of `include` vs `contain` evade me. Thanks for your input, -Alan -- 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/757357f3-c5a7-4934-8a28-9dcb25795c0fo%40googlegroups.com.
