hello, I will be releasing a module on the forge with this functionality, but need some early testers as I do not currently have a varied environment to test against.
Those interested please contact me off list or if you're brave just download the ripienaar/module_data module into your manifests, it auto activates and needs no config. Though this is 0.0.1 release no doubt will kill your kitten. ----- Original Message ----- > From: "chengkai liang" <[email protected]> > To: [email protected] > Sent: Friday, December 6, 2013 6:25:06 PM > Subject: Re: [Puppet Users] Re: Unable to specify hierarchy for > data-in-modules > > It is nice to mention this here. > > Thanks, > -Chengkai > > > On Thu, Dec 5, 2013 at 6:18 PM, Henrik Lindberg < > [email protected]> wrote: > > > On 2013-06-12 1:30, chengkai liang wrote: > > > >> Well, I can execute this with for individual module via *puppet apply > >> --binder true ...* I haven't been able to do this successfully on my > >> > >> vagrant box. I found out that vagrant use --detailed-exitcode option > >> with puppet apply, which interfere with *--binder true* option. I have > >> to set*binder true* in puppet.conf. Yet I don't have time to try that > >> yet. > >> > >> > >> > >> On Sat, Nov 30, 2013 at 11:03 AM, Steven Jonthen > >> <[email protected] <mailto:[email protected]>> wrote: > >> > > > > Please be aware that we decided to not move ahead with the "data in > > modules" implementation based on the experimental implementation that is > > turned on with --binder=true option. > > > > We found several things - there was way too much complexity being exposed > > to users, the first implementation missed support for some typical use > > cases, and the entire domain of "providing data to modules" turned out to > > be an exchange of one problem for another in several cases. > > > > Meanwhile, if you are brave, and want to experiment. You probably want my > > branches with simplifications and additional support for private data. If > > for nothing else to gain some experience regarding some of the issues. > > (Since we decided not to move ahead, these additions & changes will not be > > merged into the puppet code base, and the behavior now available via > > --binder will be removed - we have not quite yet figured out what it will > > be replaced by though). > > > > Regards > > - henrik > > > > > > -- > > You received this message because you are subscribed to a topic in the > > Google Groups "Puppet Users" group. > > To unsubscribe from this topic, visit https://groups.google.com/d/ > > topic/puppet-users/Z_6ehvPEm98/unsubscribe. > > To unsubscribe from this group and all its topics, send an email to > > [email protected]. > > To view this discussion on the web visit https://groups.google.com/d/ > > msgid/puppet-users/l7rc5f%24jbs%241%40ger.gmane.org. > > > > For more options, visit https://groups.google.com/groups/opt_out. > > > > -- > 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 [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/puppet-users/CANTbHr8NTCAspOEm9gT1xTtYOBBe_k4w_fK92foht1heikhjXA%40mail.gmail.com. > For more options, visit https://groups.google.com/groups/opt_out. > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/1021960233.953.1386370777066.JavaMail.zimbra%40devco.net. For more options, visit https://groups.google.com/groups/opt_out.
