On 11/06/2014 04:04 AM, 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. How would make use of that information on the agent if expressions are evaluated on the master? As an example, I'd like to be able to 'query' the home dir of a role account (without having to install a fact) and interpolate it into a string to form a path. I've always found this scenario a bit frustrating as the type has the data I want; it's just inaccessible while the catalog is built.
-Josh -- -- 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/545C3629.1010203%40cpan.org. For more options, visit https://groups.google.com/d/optout.
