mistral/releasenotes/notes/evaluate_env_parameter-14baa54c860da11c.yaml
Renat Akhmerov 0415a7c44b Release notes for "evaluate_env"
Change-Id: I9a164e317d3a50a2ddb42e5b20c7c2c7bdaf679f
2017-05-12 16:13:37 +07:00

17 lines
796 B
YAML

---
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.