* Custom LDAP module ``m_ldap_entry`` has been removed. Role uses

    the official ``ldap_entry`` and ``ldap_attr`` modules.

  * The ``ldap_entries`` parameter now supports only the states

    supported by ``ldap_entry`` module (e.g. ``append`` is not

    supported any longer - since it came with custom LDAP module).

New features/improvements:

* Tests have been updated to work with latest Molecule/Testinfra as

  part of the Ansible upgrade process.

2.0.0

-----

Upgrade to Ansible 2.3.x, minor bug fixes and updates needed for the upgrade.

Breaking changes:

* Switched to Ansible 2.3.x, removing support for Ansible 1.9.x. All

  documentation has been updated.

* Due to switch to Ansible 2.x which is more restrictive when deploying code on

  ``mail_server`` roles on the same server, aliases can be set-up through them.

* Sets-up system for performing checks on pip requirements files. Roles that

  want their requirements files checked should create a sub-directory inside of

  ``/etc/pip_check_requirements_upgrades``, and place ``.txt`` and ``.in`` files

  inside (with same base name). The ``.txt`` files should be standard

  requirements files with fixed versions (the ones installed by the role). The

  ``.in`` files should contain only the top-level packages (no

  dependencies). Avoid hard-coding versions in the ``.in`` file unless really

  needed. For packages where you want to stick to stable/LTS version branch, you

  should be able to use ``~=`` operator (for example ``django~=1.8.0``. Checks

  are implemented via `pip-tools <https://github.com/jazzband/pip-tools>`_ and a

  custom script that outputs diffs if upgrades are available. Script is run via

  user.

* Optionally configures time synchronisation using NTP (if

  ``ntp_servers`` parameter is set).

Role dependencies

~~~~~~~~~~~~~~~~~

Depends on the following roles:

* **backup_client**

MAILTO=root