Do not copy workflow environment into subworkflows
* We previously always copied a workflow environment of a parent
workflow into a subworkflow when starting it. However, this is
redundant because we now have 'root_execution_id' field in the
the workflow execution model so that we can always get an
environment of a subworkflow just by accessing the root execution.
It saves a lot of space in DB and increases performance in cases
when we have a large workflow environment and many subworkflows.
Reviewed: https:/ /review. openstack. org/565004 /git.openstack. org/cgit/ openstack/ mistral/ commit/ ?id=7ec98b457cb 83087241fbe5153 467946c90af099
Committed: https:/
Submitter: Zuul
Branch: stable/pike
commit 7ec98b457cb8308 7241fbe51534679 46c90af099
Author: Renat Akhmerov <email address hidden>
Date: Fri Apr 27 17:01:31 2018 +0700
Do not copy workflow environment into subworkflows
* We previously always copied a workflow environment of a parent
workflow into a subworkflow when starting it. However, this is
redundant because we now have 'root_execution_id' field in the
the workflow execution model so that we can always get an
environment of a subworkflow just by accessing the root execution.
It saves a lot of space in DB and increases performance in cases
when we have a large workflow environment and many subworkflows.
Change-Id: Id8f5e917b45fed f09ecf2d28798a6 949cf5f5c99
Related-Bug: #1757966