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
"defaults/main.yml" variables file
2. None of the variables are evaluated if one of them wouldn't be evaluated
Are these behaviors purposeful or just the result of how and when variables
are put in scope? None of these variables are related to hosts (i.e. they
are global).
I know that there is a hierarchy of variables and that they are looked for
in a certain order, but where does Ansible look for variables before
deciding how to display task names?
Thanks,
Chip
On Monday, September 15, 2014 10:32:51 PM UTC-4, Stephen Aylward wrote:
>
> When running my playbook, on tasks that I have tried to name with
> variables, the variable name is there rather than the value.
> Eg:
> TASK: [weblogic | Create {{ tmp_dir }}] **************************
>
> What do I need to change to get the tmp dir value output?
> Thanks
>
--
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/4f0bd9ef-2499-420c-a596-efab45a68d88%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
