I agree with the task object as well. It should be an object you can get info like the start time, end time, error code, ...
-----Original Message----- From: Renat Akhmerov [mailto:rakhme...@mirantis.com] Sent: יום ב 07 ספטמבר 2015 19:59 To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [mistral][yaql] Addressing task result using YAQL function > On 07 Sep 2015, at 19:18, Stan Lagun <sla...@mirantis.com> wrote: > > I believe this is a good change. $.task_name requires you that $ be > pointing to a tasks dictionary. But in the middle of the query like > [1.2.3].select($ + 1) "$" will change its value. With a function approach > you can write [1, 2, 3].select($ + task(taskName)). However the name "task" > looks confusing as to my understanding tasks may have attributes other than > result. It may make sense to use task(taskName).result instead. Yes, I like the idea that task() should be more than just a result. Good point! Renat Akhmerov @ Mirantis Inc. __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
