Deploy template fails with ``no test named 'boolean'`` about ansible-role-nginx-config HOT 5 CLOSED

Just noticed that my Jinja2 version does not fulfills the requirements.

# pip3 install Jinja2 --upgrade

ansible [core 2.11.6]
  python version = 3.6.8 (default, Sep 12 2021, 04:40:35) [GCC 8.4.1 20200928 (Red Hat 8.4.1-1)]
  jinja version = 3.0.2
  libyaml = True

Does work now!

Is there a way to implement a "requirements" check?

from ansible-role-nginx-config.

There probably is a way to implement a requirements check using the shell or command module, but there's a few other items on the roadmap with a higher priority. PRs are welcome though! 😄

from ansible-role-nginx-config.

Hi,

The Jinja version requirement breaks compatibility with the the standard execution environment in Ansible Automation Platform (Ansible Tower). A custom execution environment has to be built and maintained, just for the Jinja version requirement.

This is the default execution environment:

ansible [core 2.12.1]
  config file = /etc/ansible/ansible.cfg
  configured module search path = ['/home/runner/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /usr/lib/python3.8/site-packages/ansible
  ansible collection location = /home/runner/.ansible/collections:/usr/share/ansible/collections
  executable location = /usr/bin/ansible
  python version = 3.8.8 (default, Aug 11 2021, 06:52:42) [GCC 8.5.0 20210514 (Red Hat 8.5.0-3)]
  jinja version = 2.10.3
  libyaml = True

Would it be possible to make this role work with the standard available version of Jinja?

from ansible-role-nginx-config.

Hey @sigbjornaib!

Thanks for bringing this up! I did not realize this was the case -- let me follow up with Ansible and see if they have plans/when will they update Jinja2 to 2.11. Many of the built in checks rely on the boolean test and while they can be backported, I would rather keep it as is for code cleanliness.

from ansible-role-nginx-config.

Looks like the minimum Jinja2 version will be updated to 3.x with ansible-core 2.13 due for release sometime in spring. As such, and while I do understand that it's not ideal to have to create and maintain a custom execution environment, I don't think the best path forward is backporting these templates. I would probably advise using a pre_task to update the Jinja2 version instead.

from ansible-role-nginx-config.