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
I wouldn’t recommend using shell for this, as Ansible has the apt module designed for just this purpose. I’ve detailed using apt below. In a playbook, you can update and upgrade like so: – name: Update and upgrade apt packages become: true apt: upgrade: yes update_cache: yes cache_valid_time: 86400 #One day The cache_valid_time value can … Read more
There’s no concept of current directory in Ansible. You can specify current directory for specific task, like you did in your playbook. The only missing part was the actual command to execute. Try this: – name: Go to the folder and execute command command: chdir=/opt/tools/temp ls
NOTE: Using set_fact as described below sets a fact/variable onto the remote servers that the task is running against. This fact/variable will then persist across subsequent tasks for the entire duration of your playbook. Also, these facts are immutable (for the duration of the playbook), and cannot be changed once set. ORIGINAL ANSWER Use set_fact … Read more
Sometimes it’s knowing what to ask. I didn’t know as I am a developer who has taken on some DevOps work. Apparently ‘passwordless’ or NOPASSWD login is a thing which you need to put in the /etc/sudoers file. The answer to my question is at Ansible: best practice for maintaining list of sudoers. The Ansible … Read more
Try with the option -kK. It will prompt for password. $ ansible-playbook mail.yml -kK SSH password: BECOME password[defaults to SSH password]: -k, –ask-pass: ask for connection password -K, –ask-become-pass: ask for privilege escalation password
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
Ansible (from 1.4 onwards) already reveals environment variables for the user under the ansible_env variable. – hosts: all tasks: – name: debug through ansible.env debug: var=ansible_env.HOME Unfortunately you can apparently only use this to get environment variables for the connected user as this playbook and output shows: – hosts: all tasks: – name: debug specified … Read more
If you do not provide any path at all, just the filename, Ansible will pick it automatically from the files directory of the role. – copy: src: foo.conf dest: /etc/foo.conf Additionally, since Ansible 1.8, there is the variable role_path which you could use in your copy task. – copy: src: “{{ role_path }}/files/foo.conf” dest: /etc/foo.conf
With Ansible 2.x you can use vars: with tasks. Template test.j2: mkdir -p {{myTemplateVariable}} Playbook: – template: src=test.j2 dest=/tmp/File1 vars: myTemplateVariable: myDirName – template: src=test.j2 dest=/tmp/File2 vars: myTemplateVariable: myOtherDir This will pass different myTemplateVariable values into test.j2.