On 2014-06-11 12:04, Luke Kanies wrote:
A fourth option would be to combine the best of Resources and exported
resources: Build a querying system akin to exported resources, but
against the current system, rather than against the catalog. Or really,
take the exact same querying we already have, but provide the ability to
control where it's searching against, and what to do with the results.
This is my preferred solution. It makes querying more powerful, and
separates the concept of querying from the source of the data.
I like this a lot. There are some design challenges though as this
pushes the querying to the agent, and that this is probably best
supported at the language level rather than being expressed as a
function. (This because variables etc. in a query needs to be
evaluated/resolved in scope when the catalog is produced, just like they
are today in virtual/exported collection).
I really do think this kind of functionality should be supported at the
framework level, and more hacks like Resources aren't the best long term
solution.
Agree.
--
Visit my Blog "Puppet on the Edge"
http://puppet-on-the-edge.blogspot.se/
--
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/545BB100.8050805%40cloudsmith.com.
For more options, visit https://groups.google.com/d/optout.
