ec2_launch_template fails when volume_size is a string about community.aws HOT 8 CLOSED

@leedm777

This is not a module issue. This is because you are using jinja templating. Unfortunately due to how jinja2 works, it technically only has the ability to return strings. Any time you use jinja2 templating, the result comes out as a string. So while |int is internally converting the value to an int, the final result from jinja2 is a string. This has been discussed here: ansible/ansible#30366

The good news is there was a change implemented in jinja to preserve the native types. You can add the following in the [default] section of ansible.cfg

jinja2_native = True

With above, integer value wont convert to a string, while using jinja template. You also dont need a int filter now. Can you please try that. I was able to use your playbook (minus the int filter) successfully with above change in ansible.cfg

from community.aws.

Thank you @jainnikhil30 for the long answer. The jinja2_native configuration key is documented here https://docs.ansible.com/ansible/latest/reference_appendices/config.html#default-jinja2-native and requires Ansible 2.7 or greater and an up to date version of Jinja2 (>= 2.10).

@leedm777 I close the PR, feel free to reopen if you think we've missed something.

from community.aws.

Is there a way to do jinja2_native on just one task or play? I have a huge stack of playbooks that all expect the default behavior. Changing it so this one value converts correctly then breaks dozens of other tasks.

Based on the documentation that @goneri sent here, you can configure the environment variable at the task level so that this does not effect the entire playbook/play:

ANSIBLE_JINJA2_NATIVE: true

from community.aws.

@leedm777 Let us know if @jainnikhil30's solution works for you? Thanks.

from community.aws.

@jainnikhil30, enabling jinja2_native does indeed work.

Although given Jinja2's default behavior of "everything returns a string", I would've expected either Ansible or the module itself to be more lenient and parse strings that get passed in for numeric fields. That said, I'm good with enabling jinja2_native and moving on.

Thanks!

from community.aws.

cc @jillr @s-hertel @tremble @wimnat
click here for bot help

from community.aws.

Is there a way to do jinja2_native on just one task or play? I have a huge stack of playbooks that all expect the default behavior. Changing it so this one value converts correctly then breaks dozens of other tasks.

from community.aws.

@sky-amoncadot I very much appreciate the reply as I went looking for that specific understanding and have still yet to find documentation that clearly explains how one changes a configuration setting at the task level. I know it's a tangent to this issue, but how does one infer from Ansible Configuration Settings which of the keys used in a playbook keyword context?

• The section is labeled DEFAULT_JINJA2_NATIVE
• The ini key is jinja2_native
• The env var is ANSIBLE_JINJA2_NATIVE

Searching on other settings I've seen altered in plays, like become_user, I'm guessing it's the ini key of jinja2_native. I'm up for doing the documentation PR myself, but it just struck me odd that it's assumed knowledge.

from community.aws.