The common role at the moment uses same set of pip requirements when setting-up dedicated Python virtual environments used for running the pip requirements upgrade checks. These are based around the use of the pip-tools package.

Due to Python 3.4 being unsupported upstream, the pip-tools team has decided to drop the support for Python 3.4 as well. Majic Ansible Roles still support Debian Jessie (LTS release), which in turn uses the deprecated Python 3.4. This results in discrepancy between what version of pip-tools can be installed on Debian Jessie machines for Python 2 and Python 3 - while the current parameter used for specifying the pip-tools version to use for upgrade checks covers both.

While this will be eventually fixed by dropping support for Debian Jessie in Majic Ansible Roles itself, in interim it would be needed to add support for separate set of requirements for Python 3 virtual environment so that those can be tracked separately. This might come in handy in the future as well in case of similar issues.

The following should be done:

• Update the common role:
  • Introduce new parameter pip_check_requirements_py3.
  • Parameter should contain the pip requirements used for setting-up dedicated Python 3 virtual environment used for running the pip re requirements upgrades checks.
  • Roll-out a separate input file for pip-tools for checking package upgrades for the Python 3 virtual environment.
• Update role reference documentation.
  • Make sure to mention new parameter.
  • Make sure to mention the existing parameter is used for Python 2 only.
• Update release notes, making sure to mention introduction of new parameter as a breaking change (since it changes the behaviour of existing installations).