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/565949 /git.openstack. org/cgit/ openstack/ mistral/ commit/ ?id=9e00e002a97 a628bf3ec293fbb 8ca63127d9f84e
Committed: https:/
Submitter: Zuul
Branch: stable/queens
commit 9e00e002a97a628 bf3ec293fbb8ca6 3127d9f84e
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: Ibd66107b8b8bd9 2b8f38c299c8890 3d9dba3d9e8
Related-Bug: #1757966