Thanks Angus. One obvious thing is we either make it somewhat consistent, or name it differently. These looks similar, at least on the surface. I wonder if the feedback we’ve got so far (for-each is confusing because it brings wrong expectations) is applicable to Heat, too.
Another observation on naming consistency - mistral uses dash, like `for-each`. Heat uses _underscores when naming YAML keys. So does TOSCA standard. We should have thought about this earlier but it may be not late to fix it while v2 spec is still forming. DZ. On Dec 18, 2014, at 9:07 PM, Angus Salkeld <asalk...@mirantis.com> wrote: > On Mon, Dec 15, 2014 at 8:00 PM, Nikolay Makhotkin <nmakhot...@mirantis.com> > wrote: > Hi, > > Here is the doc with suggestions on specification for for-each feature. > > You are free to comment and ask questions. > > https://docs.google.com/document/d/1iw0OgQcU0LV_i3Lnbax9NqAJ397zSYA3PMvl6F_uqm0/edit?usp=sharing > > > > Just as a drive by comment, there is a Heat spec for a "for-each": > https://review.openstack.org/#/c/140849/ > (there hasn't been a lot of feedback for it yet tho') > > Nice to have these somewhat consistent. > > -Angus > > > -- > Best Regards,Nikolay > > _______________________________________________ > 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
_______________________________________________ OpenStack-dev mailing list OpenStackemail@example.com http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev