Hi Winson, I think it makes perfect sense. The reason I think is mostly historical and this can be reviewed now. Can you pls file a BP and describe your suggested design on that? I mean how we need to alter interface Action etc.
Thanks Renat Akhmerov @ Mirantis Inc. > On 09 Dec 2014, at 13:39, W Chan <m4d.co...@gmail.com> wrote: > > Renat, > > Is there any reason why Mistral do not pass action context such as workflow > ID, execution ID, task ID, and etc to all of the action executions? I think > it makes a lot of sense for that information to be made available by default. > The action can then decide what to do with the information. It doesn't > require a special signature in the __init__ method of the Action classes. > What do you think? > > Thanks. > Winson > _______________________________________________ > 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