On Thu, Mar 12, 2015 at 10:20 AM, Rick Kasten wrote:
> These answers don't make sense to me. Here's what I've got:
>
> # inventory/dse/group_vars/dse/
> package_versions.yml
> package_versions:
> app:
> oraclejre_version: jdk1.7.0_75
>
> # roles/oraclejre/tasks/main.yml
> - name: OracleJRE |
This is a bug: https://github.com/ansible/ansible/issues/10347
The variable handling changed and the callback isn't getting the
variables it needs anymore. Defered to v2 because one of the goals of
v2 is to simplify variable handling which should make this easier to
fix. (and any fix that was to
Except this fails to work even with global vars on 1.8.4 (but used to print
the value with 1.7.x).
---
- hosts: 127.0.0.1
gather_facts: no
vars:
vhost: "foo"
tasks:
- name: create a virtual host file for {{ vhost }}
debug: msg="{{ vhost }}"
Why
These answers don't make sense to me. Here's what I've got:
# inventory/dse/group_vars/dse/
package_versions.yml
package_versions:
app:
oraclejre_version: jdk1.7.0_75
# roles/oraclejre/tasks/main.yml
- name: OracleJRE | Make OracleJRE {{ version }} home directory
file: path=/usr/local/jav
These answers don't make sense to me. Here's what I've got:
# inventory/dse/group_vars/dse/package_versions.yml
package_versions:
app:
oraclejre_version: jdk1.7.0_75
# roles/oraclejre/tasks/main.yml
- name: OracleJRE | Make OracleJRE {{ version }} home directory
file: path=/usr/local/java
Basically think of it as each variable (for a large infrastructure)
basically having 500 different values
Ansible can't tell the variable has only *one* value, since the variable is
"inventory scope" as such, it can't plug it in, because the task header
(that preceeds the next 500 task results) wo
short answer: yes, this is expected behaviour
long one:
#1 happens because of main/defaults.yml has the lowest precedence
possible and vars there don't get merged in until task execution,
name: gets set during task definition, this is because host vars are
allowed to override them. You can use var
To expand on this, I have a task with 3 variable references in its name.
- name: Send messages, count {{msgcount}}, size {{msgsize}}, port
{{msgport}}
shell: some_command
I've noticed a couple behaviors with evaluating these:
1. The variable is not evaluated if only defined in the role's
"de
