Hi,
On May 5, 2016 8:14 AM, "Rob White" wrote:
>
> Hi all,
>
> This is mostly aimed at the core team...
>
> Can you explain why the file lookup plugin changes the contents of the
file as far as quotes are concerned? I.e. it changes all double quotes to
single quotes.
>
> I am not sure if it used
Hi,
I have couple PRs waiting in modules-extras and I would love to get some
community review on them so we can ship them if possible. I regularly use
and test all of them. Would it be possible to get someone from community to
have a look and maybe give me some feedback/shipit ?
https://github
Hi,
There is no such filter for that but you can do that with if. IMHO jinja
template is not right place for validating variable values. Much better
place would be playbook.
On Tue, Feb 21, 2017 at 12:26 PM, vu001 wrote:
> Hi,
>
> is it possible in Jinja2 template to define possible values for
Hi,
Not able to raise an error would be one of reasons to not do it in
template. Can you share more about your setup that could help.
On Tue, Feb 21, 2017 at 3:14 PM, vu001 wrote:
> How would you do that in playbook...
> My playbook has only a few lines, all logic is done in templates.
> I have
need to have a filter per variable
3) Simple data verification can be done this way
https://gist.github.com/haad/b005de9bd6e7fef2d8b744de55473eab#file-verification-input-yaml
4) I have also done variable validation with json schema it looked like
this
https://gist.github.com
Hi,
You are overwriting test_tasks variable. Variables in ansible re in one
global namespace. Therefore debian included version will probably overwrite
centos one.
My general suggestion would be to avoid such techniques as it will make
role much harder to understand. If role would rather create r
