ansible

The pause module actually does exactly that. But it does not give you an option to answer yes or no. Instead it expects the user to press Ctrl+C and then a for abort. To continue the user simply needs to press Enter. Since this is not perfectly obvious to the user you can describe it … Read more

Using Ansible modules, you don’t need to check if something exist or not, you just describe the desired state, so: – name: create directory if they don’t exist file: path: “{{ item }}” state: directory owner: root group: root mode: 0775 loop: – /data/directory – /data/another

Both vars_files and include_vars are labeled as stable interfaces so neither of them are deprecated. Both of them have some commonalities but they solve different purposes. vars_files: vars_file directive can only be used when defining a play to specify variable files. The variables from those files are included in the playbook. Since it is used … Read more

Good news- in a basic use case, this is fairly easy. Simply use the ansible_ssh_private_key_file parameter in your Ansible inventory. Here are some examples purloined from my personal file: $ cat hosts.ini [server1] 54.1.2.3 ansible_ssh_private_key_file=~/.ssh/server1.pem [testservers] ec2-54-2-3-4.compute-1.amazonaws.com ansible_ssh_private_key_file=~/.ssh/aws-testserver.pem ansible_ssh_user=ubuntu ec2-54-2-3-5.compute-1.amazonaws.com ansible_ssh_private_key_file=~/.ssh/aws-testserver.pem ansible_ssh_user=ubuntu [piwall] 10.0.0.88 ansible_ssh_private_key_file=~/.ssh/raspberrypi.pem ansible_ssh_user=pi

As nikobelia pointed out in the comments, grep returns an exit code of 1 when it doesn’t match any lines. Ansible then interprets this (actually any status code other than 0 from a shell/command task) as an error and so promptly fails. You can tell Ansible to ignore the response code from the shell/command task … Read more

Add stdout_callback=debug and stderr_callback=debug in the defaults section of your ansible.cfg file. [defaults] (…) stdout_callback=debug stderr_callback=debug This is supported by ansible > 2.0

Now supported as of Ansible 2.3.0: – name: myrole with_items: – “aone” – “atwo” include_role: name: myrole vars: thing: “{{ item }}”

The variable I was searching for is a built in feature: inventory_hostname Ansible documentation about inventory_hostname and inventory_hostname_short is found from chapter Magic Variables, and How To Access Information About Other Hosts. Original question: https://groups.google.com/forum/#!topic/ansible-project/Oa5YXjHecIw