We've got a set of playbooks that we use to set up production, testing and
development environments for a project.
A very useful pattern on which we rely heavily is using template source
directory names based on inventory_hostname, e.g:
- name: copy over nginx config for some site
template:
Upgrading from 1.9.5 to 2.0.1.0 without changing the playbook, a task fails
that used to work.
The error:
[DEPRECATION WARNING]: Skipping task due to undefined Error, in the future
this will be a fatal error.. This feature will be removed in a
future release. Deprecation warnings can be
A playbook that runs fine on Ansible 1.9.5 suddenly fails on 2.0 with the
following error (sensitive details hidden):
$ *ansible-playbook deploy.yml -i inventory_dev.py -*
Using /Users/[...]/ansible.cfg as config file
SUDO password:
Loaded callback default of type stdout, v2.0
3 plays in
Hi James,
Thanks for your help! You put me on the right track. Here's what I ended up
doing (in case someone else finds this useful).
First, for DRY's sake, I collected the absolute paths to the apt keys in
group_vars/all to make them global and role-independent, in a form that
could be
I'm new to Ansible, and trying to wrap my head around the variety of ways
to organize playbooks and achieve certain tasks in a DRY way, without
duplicating too much logic in several places.
Right now I'm trying to find a way in which I could have with_fileglob
consolidate
files of a certain
