Hi Brian,
proxy_env is a dict defined in inventory/group/all files. I have the code:
- name: Install postgres93
yum: name={{item}} state=present
with_items:
- "{{cron_pkgname}}"
- "{{mail_pkgname}}"
- rdiff-backup
- which
- postgresql93-server
- postgresql93-contrib
environment: proxy_env
that works with version 1.9.x
But v2 refuse to run that code saying expected a dict and got proxy_env.
When I switch to env: proxy_env it stopped complaining about it. Probably
it is still error at this but give different error message.
How do I specify proxy_env in v2? Or is it a bug?
On Wednesday, January 20, 2016 at 2:56:06 AM UTC+10, Brian Coca wrote:
>
> env: proxy_env?
>
> there is no such directive, i'm guessing you want:
>
> environment: "{{proxy_env}}"
>
> 2.0 is now better at validating playbooks and unlike previous
> versions it does not ignore incorrect entries. The error message
> itself seems a bit confusing, but it does point at the correct task.
>
>
>
> --
> Brian Coca
>
--
You received this message because you are subscribed to the Google Groups
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/ansible-project/6db7fbdf-5c96-4d9a-b89b-5cffd3c0f872%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
