openstack
/
mistral
Code Issues Proposed changes

Merge "Release notes for "evaluate_env"" into stable/ocata

This commit is contained in:
Jenkins 2017-05-15 09:40:01 +00:00 committed by Gerrit Code Review
parent 74119eea1e 88f82e91fb
commit 3d8ebf1bf3
1 changed files with 16 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
releasenotes/notes/evaluate_env_parameter-14baa54c860da11c.yaml Normal file
View File

@ -0,0 +1,16 @@
---
fixes:
- When we pass a workflow environment to workflow parameters
using 'env' Mistral first evaluates it assuming that it
can contain expressions (YAQL/Jinja) For example, one
environment variable can be expressed through the other.
In some cases it causes problems. For example, if the
environment is too big and has many expressions, especially
something like <% $ %> or <% env() %>. Also, in some cases
we don't want any evaluations to happen if we want to
have some informative text in the environment containing
expressions.
In order to address that the 'evaluate_env' workflow parameter
was added, defaulting to True for backwards compatibility.
If it's set to False then it disables evaluation of
expressions in the environment.