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