Jinja2 templates and undefined variables

[NotSqrt]

Hello,

I've had problems experimenting with Pillar : I had configured it badly, so my templates were using empty variables resulting in a rather bad situation on my test server ...

A few things in the tutorial/documentation that would have helped me : 

• a more visible presence of the command pillar.data
• some explanations on the option test, for commands like state.highstate

I ended up using the UndefinedException from Jinja to track undefined variables / keys in dict, and raise errors. (see git diff as attachment).

It might be useful for someone else!

Thanks

[Thomas S Hatch]

Hi NoSqrt,

This is good info, and a good patch. I think that we need to have a more clear system for debugging pillar, I added an issue to github (https://github.com/saltstack/salt/issues/1838) for it and I would be happy to merge this patch and probably some more systems to make this clearer.

Can I persuade you to make a pull request on github so we can better track the changes?

[Not Sqrt]

Hello,

No problem for a pull request, I'll look into it in the next few days.

My patch might be too strict : one may want to be able to use undefined variables in templates ! So I'm not 100% certain that it's a good idea to make this mandatory.

There may be a way to make this optional ?

2012/8/16 Thomas S Hatch <that...@gmail.com>

[Thomas S Hatch]

Good call, I think that what we really need is to make it more trackable, so that an undefined variable would log errors but maybe not halt the renderer