Agree with Nikolay. Winson, did you see https://blueprints.launchpad.net/mistral/+spec/mistral-execution-environment <https://blueprints.launchpad.net/mistral/+spec/mistral-execution-environment> ? The concept described their is pretty simple and syntactically we can have a predefined key in workflow context, for example accessible as $.__env (similar to $.__execution), which contains environment variables. They are the same for the whole workflow including subworkflows.
One additional BP that we filed after Paris Summit is https://blueprints.launchpad.net/mistral/+spec/mistral-workflow-constants <https://blueprints.launchpad.net/mistral/+spec/mistral-workflow-constants> which is a little bit related to it. According to what described in this BP we can just define workflow scoped constants for convenience which are accessible as regular workflow input variables. Btw, as an idea: they can be initilalized by variables from execution environment. And there’s even one more BP https://blueprints.launchpad.net/mistral/+spec/mistral-default-input-values <https://blueprints.launchpad.net/mistral/+spec/mistral-default-input-values> that suggests having default workflow input values that is related to those two. Btw, it can be extended to having default values for action input values as well. So, I would suggest you take a look at all these BPs and continue to discuss this topic. I feel it’s really important since all these things are intended to improve usability. Thanks Renat Akhmerov @ Mirantis Inc. > On 10 Dec 2014, at 00:17, Nikolay Makhotkin <nmakhot...@mirantis.com> wrote: > > Guys, > > May be I misunderstood something here but what is the difference between this > one and > https://blueprints.launchpad.net/mistral/+spec/mistral-execution-environment > <https://blueprints.launchpad.net/mistral/+spec/mistral-execution-environment> > ? > > On Tue, Dec 9, 2014 at 5:35 PM, Dmitri Zimine <dzim...@stackstorm.com > <mailto:dzim...@stackstorm.com>> wrote: > Winson, > > thanks for filing the blueprint: > https://blueprints.launchpad.net/mistral/+spec/mistral-global-context > <https://blueprints.launchpad.net/mistral/+spec/mistral-global-context>, > > some clarification questions: > 1) how exactly would the user describe these global variables syntactically? > In DSL? What can we use as syntax? In the initial workflow input? > 2) what is the visibility scope: this and child workflows, or "truly global”? > 3) What are the good default behavior? > > Let’s detail it a bit more. > > DZ> > > > > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org <mailto:OpenStack-dev@lists.openstack.org> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev> > > > > > -- > Best Regards, > Nikolay > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
