I like this approach and seems to have greater utility beyond the original proposal. I'm not fussed on YAQL or straight up JSONPath, but something along those lines seems to make sense.
On Nov 11, 2014, at 9:35 AM, Alexis Lee <alex...@hp.com> wrote: > Alexis Lee said on Mon, Nov 10, 2014 at 05:34:13PM +0000: >> How about we support YAQL expressions? https://github.com/ativelkov/yaql >> Plus some HOFs (higher-order functions) like cond, map, filter, foldleft >> etc? > > We could also use YAQL to provide the HOFs. > >> Here's first_nonnull: >> >> config: >> Fn::Select >> - 0 >> filter: >> - yaql: "$.0 != null" >> - <item1> >> - <itemN> > > config: > yaql: "$[$ != null]" > - <item1> > - <itemN> > > This approach requires less change to Heat, at the price of learning > more YAQL. > > > Alexis > -- > Nova Engineer, HP Cloud. AKA lealexis, lxsli. > > _______________________________________________ > OpenStack-dev mailing list > OpenStackfirstname.lastname@example.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev _______________________________________________ OpenStack-dev mailing list OpenStackemail@example.com http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev