Le 19/12/2013 23:39, Jeff Bachtel a écrit :
In the end, even just the behavior change to "puppet resource" makes
the patch a non-starter because it is a widely used feature.
I understand this feature should be kept, but that a pity this should
impact other even more useful feature like "apply" or "agent".
Could it be possible that "puppet resource" and other like "apply" or
"agent" retrieves only what they need? In apply/agent case, this come
from a transaction being applied. For "puppet resource" I assume this
is not the case. Could method parameter solve this case? And this
could even keep the compat if this param is not specified
Anyway, please find attached a diff containing the changes in
question. Feel free to refine and submit it as a PR, my Ruby really
isn't up for my doing so myself.
I was also thinking doing the same kind of proof of concept.
But I would have slightly change the way the default values are passed.
Apart those changes, I think this shows we can address the different
concerns which were raised previously.
Assuming this patch is clean/adapted, is this something Puppet could
accept? or there is still other problems?
Aurélien
--
You received this message because you are subscribed to the Google Groups "Puppet
Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-dev/52B45720.5050407%40cea.fr.
For more options, visit https://groups.google.com/groups/opt_out.
