Right now, this is the only way – name: Ensures {{project_root}}/conf dir exists file: path={{project_root}}/conf state=directory – name: Copy file template: src: code.conf.j2 dest: “{{project_root}}/conf/code.conf”
Due to the fact that I answered this in 2014, I have updated my answer to account for more recent versions of ansible. Yes, you can do it at the host/inventory level (Which became possible on newer ansible versions) or global level: inventory: Add the following. ansible_ssh_common_args=”-o StrictHostKeyChecking=no” host: Add the following. ansible_ssh_extra_args=”-o StrictHostKeyChecking=no” hosts/inventory … Read more
You should use a requirements.yml file for this use-case. Describe the roles you require, using any of a variety of install methods: # Install a role from the Ansible Galaxy – src: dfarrell07.opendaylight # Install a role from GitHub – name: opendaylight src: https://github.com/dfarrell07/ansible-opendaylight # Install a role from a specific git branch – name: … Read more
You can use the playbook_dir variable. See the documentation about magic variables.
From the ansible docs: If a required variable has not been set, you can skip or fail using Jinja2’s defined test. For example: tasks: – shell: echo “I’ve got ‘{{ foo }}’ and am not afraid to use it!” when: foo is defined – fail: msg=”Bailing out. this play requires ‘bar'” when: bar is not … Read more
You can use Jinja’s default: – name: Create user user: name: “{{ my_variable | default(‘default_value’) }}”
There are two options that you can add to the [defaults] section of the ansible.cfg file that will control whether or not .retry files are created and where they are created. [defaults] … retry_files_enabled = True # Create them – the default retry_files_enabled = False # Do not create them retry_files_save_path = “~/” # The … Read more
The necessary variable is inventory_hostname. – name: Install this only for local dev machine pip: name=pyramid when: inventory_hostname == “local” It is somewhat hidden in the documentation at the bottom of this section.
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
From the FAQ: How do I see a list of all of the ansible_ variables? Ansible by default gathers “facts” about the machines under management, and these facts can be accessed in playbooks and in templates. To see a list of all of the facts that are available about a machine, you can run the … Read more