Hi,
On 16.05.2014 02:17, Alessandro Franceschi wrote:
On Thursday, May 15, 2014 9:55:05 PM UTC+2, John Bollinger wrote:
On Thursday, May 15, 2014 9:46:40 AM UTC-5, Alessandro Franceschi wrote:
Hallo everybody,
I've tried to look around in the group for past discussions
about this topic but haven't found any.
If this has been already debated , please forgive me and point
me to the right direction.
I wonder what do you thing about a feature request to have data
bindings also for defines' parameters.
I'm skeptical about their value. We already have data bindings for
classes, by which resource parameters can (indirectly) be injected,
and I am inclined to think that classes are the right level of
abstraction. On the other hand, we also have create_resources(),
which already can give you resource-level data binding if you want
to use it that way.
I do not favor drawing distinctions between defined resource types
and native resource types. On that basis, I would argue for data
binding either for all resource types or for none, and against data
binding for only defined types.
I am concerned about the impact. It is already somewhat costly for
Puppet to evaluate data bindings for class parameters, and adding
bindings for resource parameters (even just for resources of defined
types) will magnify that. Note that the cost scales with the
aggregate number of defined parameters for all declared resources,
independent whether any data are actually bound. In fact, the cases
were no data are bound are the most costly, because hiera must then
search the entire hierarchy.
Yes, these are valid and convincing points.
Anyway if we find data binding useful for classes and can bear the
performance overhead, I suppose we can do the same for defined types.
I very much like the idea for data binding on all parameters, but this
statement is really not universally true. I've got catalogs with only
tens of classes but thousands of resources. That works out to 100x more
hiera calls. :-/
Regards, David
--
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/5375A109.7020209%40dasz.at.
For more options, visit https://groups.google.com/d/optout.
