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 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/l7rc5f%24jbs%241%40ger.gmane.org.
For more options, visit https://groups.google.com/groups/opt_out.
