Skip to content
This repository has been archived by the owner on Jun 13, 2020. It is now read-only.

Stop ignoring missing object variables #113

Open
otakup0pe opened this issue Jul 11, 2017 · 0 comments
Open

Stop ignoring missing object variables #113

otakup0pe opened this issue Jul 11, 2017 · 0 comments

Comments

@otakup0pe
Copy link
Contributor

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,

# var file
foo:
- val1: test1
  val2: test2
- val1: test3
#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.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant