Jeff McCune <[email protected]> writes:
> On Tue, Aug 31, 2010 at 2:26 PM, Luke Kanies <[email protected]> wrote:
> [snip]
>
>>> To me, some sort of API between fact storage and third party applications
>>> would be desirable, but whatever form it took would be pretty much fine.
>>>
>>> We don't so much care about talking to facter, as obtaining the
>>> information that is stored in a specific fact, possibly from a specific
>>> node.
>
> When this happens, I'd also like to make sure we don't hard code it to
> lookup against specific nodes, but rather a subset of all nodes.
[...]
> I think simple selections like this will cover the majority of cases. This
> begs the question, "Can I specify multiple criteria?" i.e. complex joins,
> but that can wait until later because it's a rare use case as far as I can
> tell.
FWIW, the search features that Chef offers through their integration of
Apache SOLR and the use of JSON for their equivalent of stored configs is
pretty attractive looking.
However, yeah: being able to specify complex criteria and retrieve complex
information would be highly desirable to me, because I miss it every now and
then. Nothing I can't work around, but...
Daniel
--
✣ Daniel Pittman ✉ [email protected] ☎ +61 401 155 707
♽ made with 100 percent post-consumer electrons
--
You received this message because you are subscribed to the Google Groups
"Puppet Developers" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/puppet-dev?hl=en.
