Re: [Puppet Users] merging in-module default data with role-profile parameters

2017-07-17 Thread R.I.Pienaar
On Mon, Jul 17, 2017, at 11:12, Luke Bigum wrote: > On Friday, 14 July 2017 17:17:03 UTC+1, R.I. Pienaar wrote: > > > > > > I have not really found a elegant solution, and I think the right way is > > to stick this stuff in hiera on the mcollective::server_config key > > rather than try and set

Re: [Puppet Users] merging in-module default data with role-profile parameters

2017-07-17 Thread Luke Bigum
On Friday, 14 July 2017 17:17:03 UTC+1, R.I. Pienaar wrote: > > > I have not really found a elegant solution, and I think the right way is > to stick this stuff in hiera on the mcollective::server_config key > rather than try and set it via the params. > > You're not doing anything programatic a

Re: [Puppet Users] merging in-module default data with role-profile parameters

2017-07-14 Thread R.I.Pienaar
On Fri, Jul 14, 2017, at 18:12, Luke Bigum wrote: > Hello, > > I've come across an issue with how I want to write profiles vs how a > module > chooses to structure their default data. As an example, > the choria-io/puppet-mcollective module uses hashes of in-module data for > each configurat

[Puppet Users] merging in-module default data with role-profile parameters

2017-07-14 Thread Luke Bigum
Hello, I've come across an issue with how I want to write profiles vs how a module chooses to structure their default data. As an example, the choria-io/puppet-mcollective module uses hashes of in-module data for each configuration file (which is quite elegant, reduces the amount of templates