<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Yes meant to ask for consistency of referencing to task results. So it’s task(task_name) regardless of where. <div><br></div><div>One use case in favor of this is tooling: I refactor workflow with an automated tool which wants to automatically rename the task name EVERYWHERE. You guys know well by now that renaming the task is a source of too many frustrating errors :)</div><div><br></div><div>What other think? </div><div><br></div><div>DZ. </div><div><br><div><div>On Sep 3, 2015, at 4:23 AM, Renat Akhmerov <<a href="mailto:rakhmerov@mirantis.com">rakhmerov@mirantis.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><meta http-equiv="Content-Type" content="text/html charset=windows-1252"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div apple-content-edited="true" class=""><br class=""></div><div><blockquote type="cite" class=""><div class="">On 02 Sep 2015, at 21:01, Dmitri Zimine <<a href="mailto:dzimine@stackstorm.com" class="">dzimine@stackstorm.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html charset=windows-1252" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Agree, <div class=""><br class=""></div><div class="">with one detail: make it explicit - task(task_name). </div></div></div></blockquote><div><br class=""></div><div>So do you suggest we just replace res() with task() and it looks like</div><div><br class=""></div><div>task() - get task result when we are in “publish”</div><div>task(task_name) - get task result from anywhere</div><div><br class=""></div><div>?</div><div><br class=""></div><div>Is that correct you mean we must always specify a task name? The reason I’d like to have a simplified form (w/o task name) is that I see a lot of workflows that we have to repeat task name in publish so that it just look too verbose to me. Especially in case of very long task name.</div><div><br class=""></div><div>Consider something like this:</div><div><br class=""></div><div>tasks:</div><div><div> <b class="">get_volumes_by_names</b>:</div><div> with-items: name in <% $.vol_names %></div><div> workflow: get_volume_by_name name=<% $.name %></div><div> publish:</div><div> volumes: <% $.<b class="">get_volumes_by_names</b> %></div><div><br class=""></div><div>So in publish we have to repeat a task name, there’s no other way now. I’d like to soften this requirement, but if you still want to use task names you’ll be able to.</div><div><br class=""></div></div><br class=""><blockquote type="cite" class=""><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">res - we often see folks confused by result of what (action, task, workflow) although we cleaned up our lingo: action-output, task-result, workflow-output…. but still worth being explicit.</div><div class=""><br class=""></div><div class="">And full result is being thought as the root context $.</div><div class=""><br class=""></div><div class="">Publishing to global context may be ok for now, IMO.</div></div></div></blockquote></div><br class=""><div class="">Not sure what you meant by "Publishing to global context”. Can you clarify please?</div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><div class="">Renat Akhmerov</div><div class="">@ Mirantis Inc.</div></div><div class=""><br class=""></div></div>__________________________________________________________________________<br>OpenStack Development Mailing List (not for usage questions)<br>Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org">OpenStack-dev-request@lists.openstack.org</a>?subject:unsubscribe<br><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br></blockquote></div><br></div></body></html>