For those who don't know 100% of guys behind YAQL are also active OpenStack contributors. During (early) Kilo cycle we plan to release YAQL version 1.0 on stackforge. This release is going to fix some flaws in early versions, add some more flexibility and have very high UT coverage. There are at least 2 projects in OpenStack that already make heavy use of YAQL: Mistral and Murano. If Heat team decides to use YAQL as well we will be glad to help integrate it smoothly with HOT as well as make sure that YAQL 1.0 is aligned with Heat use cases.
Sincerely yours, Stan Lagun Principal Software Engineer @ Mirantis <sla...@mirantis.com> On Wed, Nov 12, 2014 at 12:32 AM, Angus Salkeld <asalk...@mirantis.com> wrote: > > > On Wed, Nov 12, 2014 at 1: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. >> > > +1 to YAQL > > > -Angus > > >> >> >> 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 > >
_______________________________________________ OpenStack-dev mailing list OpenStackfirstname.lastname@example.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev