e to loan you
the keys to the Delorian… then you can delete the post before it was
even created.
--
Stuart Longland (aka Redhatter, VK4MSL)
I haven't lost my mind...
...it's backed up on a tape somewhere.
--
You received this message because you are subscribed to the Google Groups
"A
s a
superset of JSON in fact. Ansible uses its syntax to define a language
on top.
They could have equally used XML or JSON to do this. They chose YAML.
--
Stuart Longland (aka Redhatter, VK4MSL)
I haven't lost my mind...
...it's backed up on a tape somewhere.
--
You received this message
ng it *back*
to a `str`.
>From `jinja2`'s perspective, there's no such thing as the "Ansible way",
it's *all* Python. I therefore have trouble understanding what's
happening behind the scenes.
--
Stuart Longland (aka Redhatter, VK4MSL)
I haven't lost my mind...
...it's backed up
On 11/12/18 6:07 pm, Kai Stian Olstad wrote:
> On 10.12.2018 23:26, Stuart Longland wrote:
>>> encrypted: "{{hostvars[item].get('encrypted','false') ==
>>> 'true'}}"
>>> volume_size: "{{hostvars[item].get('volume_size',100) | int}}&qu
stvars[item].get('volume_size',100) | int}}"
> volume_type: "{{hostvars[item].get('volume_type','gp2')}}"
I got the same error.
I suspect that the integer is then getting cast *back* to a string
before being passed onto `boto3`, which is then barfing on it.
Is there a way to tell
