You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 13, 2020. It is now read-only.
When passing in a complex structure, it seems that aomi doesn't mind if it's sub variables are missing. We want to enforce the use of the Jinja2 default filter for default variables - not fall back to an empty string.
#Secretfile
mounts:
{% for v in foo %}
- path: "{{v.val1}}/{{v.val2}}"
{% endfor -%}
This example will result in two mountpoints being created - test1/test2 and test3 when in reality we would want this specific example to fail based on val2 not being set.
The text was updated successfully, but these errors were encountered:
When passing in a complex structure, it seems that aomi doesn't mind if it's sub variables are missing. We want to enforce the use of the Jinja2
default
filter for default variables - not fall back to an empty string.For example,
This example will result in two mountpoints being created -
test1/test2
andtest3
when in reality we would want this specific example to fail based onval2
not being set.The text was updated successfully, but these errors were encountered: