The system roles team has had two issues reported related to variables having different types in Jinja templates:
https://github.com/linux-system-roles/timesync/pull/154 https://github.com/willshersystems/ansible-sshd/issues/188 Both issues appear to be related to some interaction between Jinja 3.0 and ansible-core 2.1x My question is: what should we do about this in the system roles? Do we really have to go through all of our Jinja template code and ensure variables are "cast" to their correct type? Do we have to add requirements.txt, bindep, etc. to ensure that only the correct combinations of ansible-core and Jinja are used? Both of these solutions seem wrong to me, unless we have been using variables incorrectly in Jinja for years now, and we really should have been "casting" the types all along. -- You received this message because you are subscribed to the Google Groups "Ansible Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to ansible-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-devel/CALF5A-KdPpse%2BBXmsjkVPn7rAQWXLN0DR_W0MHYeDF4HUMvtHw%40mail.gmail.com.
