with_items (and the whole family of with_ loops) is a dictionary key defined in a task, not as a parameter to the action. Fix the indentation: – debug: msg: “Instance: {{ item.instances }}” with_items: “{{ elb_facts.elbs }}”
The fail directive has to be used at the task level. This means that to get your desired effect, you would have to do something like — vars_prompt: – name: “var1” prompt: “Please pass variable” private: no tasks: – fail: msg=”var1 is not passed or blank” when: var1 is undefined or ( var1 is defined … Read more
Yes, there is a cleaner way. You can set environment variables per task: tasks: – shell: echo JAVA_HOME is $JAVA_HOME environment: JAVA_HOME: /usr/java/jre1.8.0_51 register: shellout – debug: var=shellout Output: TASK: [shell echo JAVA_HOME is $JAVA_HOME] ********************************** changed: [localhost] TASK: [debug var=shellout] **************************************************** ok: [localhost] => { “var”: { “shellout”: { “changed”: true, “cmd”: “echo JAVA_HOME … Read more
Simplified answer from link I mentioned in the comment: — – hosts: centos-target gather_facts: no tasks: – shell: “(cd /; python -mSimpleHTTPServer >/dev/null 2>&1 &)” async: 10 poll: 0 Note subshell parentheses. Update: actually, you should be fine without async, just don’t forget to redirect stdout: – name: start simple http server in background shell: … Read more
Solution join filter works on lists, so apply it to your list: – name: Concatenate the public keys set_fact: my_joined_list: “{{ my_list | join(‘\n’) }}” Explanation While my_list in your example is a list, when you use with_items, in each iterationitem is a string. Strings are treated as lists of characters, thus join splits them. … Read more
If you have a variable like vars: myvar: xxx xxx_var: anothervalue the working Ansible syntax: – debug: msg={{ vars[myvar + ‘_var’] }} will give you the analogue of: – debug: msg={{ xxx_var }}
Try this option. You’ll love it. There’s a new YAML callback plugin introduced with Ansible 2.5 — meaning any machine running Ansible 2.5.0 or later can automatically start using this format without installing custom plugins. To use it, edit your ansible.cfg file (either globally, in /etc/ansible/ansible.cfg, or locally in your playbook/project), and add the following … Read more
Now supported as of Ansible 2.3.0: – name: myrole with_items: – “aone” – “atwo” include_role: name: myrole vars: thing: “{{ item }}”
As advised in the Frequently Asked Questions of Ansible, moustache do not stack. Another rule is ‘moustaches don’t stack’. We often see this: {{ somevar_{{other_var}} }} The above DOES NOT WORK as you expect, if you need to use a dynamic variable use the following as appropriate: {{ hostvars[inventory_hostname][‘somevar_’ ~ other_var] }} For ‘non host … Read more
You can either change the sudo config for the user owen with this command: sudo visudo -f /etc/sudoers and change the line with user owen to this: owen ALL=(ALL) NOPASSWD:ALL then sudo won’t require Ansible to enter the password. Or you could instruct Ansible to ask you for the password with the parameter –ask-become-pass like … Read more