With Ansible 1.9 or later Ansible uses the become, become_user, and become_method directives to achieve privilege escalation. You can apply them to an entire play or playbook, set them in an included playbook, or set them for a particular task. – name: checkout repo git: repo=https://github.com/some/repo.git version=master dest={{ dst }} become: yes become_user: some_user You … Read more
Reason #1 You are using an older version of Ansible which did not have the module you try to run. How to check it? Open the list of modules module documentation and find the documentation page for your module. Read the header at the top of the page – it usually shows the Ansible version … Read more
The problem you’re running into is that you’re trying to reference facts/variables of one host from those of another host. You need to keep in mind that in Ansible, the variable foo assigned to the host localhost is distinct from the variable foo assigned to the host main or any other host. If you want … Read more
The docs strongly recommend against setting the sudo password in plaintext: As a reminder passwords should never be stored in plain text. For information on encrypting your passwords and other secrets with Ansible Vault, see Encrypting content with Ansible Vault. Instead you should be using –ask-become-pass on the command line when running ansible-playbook Previous versions … Read more
command: executes a remote command on the target host, in the same shell of other playbook’s tasks. It can be used for launch scripts (.sh) or for execute simple commands. For example: – name: Cat a file command: cat somefile.txt – name: Execute a script command: somescript.sh param1 param2 shell: executes a remote command on … Read more
You have two options to use source with ansible. One is with the “shell:” command and /bin/sh (the ansible default). “source” is called “.” in /bin/sh. So your command would be: – name: source bashrc sudo: no shell: . /home/username/.bashrc && [the actual command you want run] Note you have to run a command after … Read more
You can not do that. Variables will always override variables with the same name. The only thing you could do with this exact setup is to write your own vars plugin which reads those files and merges them into an array. If you are open to change the structure of your apps definition you can … Read more
To get first item of the list: – debug: msg: “First item: {{ ansible_processor[0] }}” Or: – debug: msg: “First item: {{ ansible_processor | first }}”
Hows this – hosts: localhost vars: war_files: server1: – file1.war – file2.war server2: – file1.war – file2.war – file3.war tasks: – name: Loop over subelements of the dictionary debug: msg: “Key={{ item.0.key }} value={{ item.1 }}” loop: “{{ war_files | dict2items | subelements(‘value’) }}” dict2items, subelements filters are coming in Ansible 2.6. FYI, if a … Read more
Use check_mode, register and failed_when in concert. This fails the task if the lineinfile module would make any changes to the file being checked. Check_mode ensures nothing will change even if it otherwise would. – name: “Ensure /tmp/my.conf contains ‘127.0.0.1’” lineinfile: name: /tmp/my.conf line: “127.0.0.1” state: present check_mode: yes register: conf failed_when: (conf is changed) … Read more