The create and destroy playbooks are not required anymore.
They are part of molecule (for docker).

When installing conda with the installer, conda can be updated by using
conda. But when using the RPM, conda should only be updated with yum.

The RPMs provided by conda are currently updated very seldomly (conda
4.6.11 is available, but the only rpm available is still 4.5.12).
Using the installer gives better control of the version we want to
install.

1. It's easier to use a mirror (no need to manually copy new RPMs to
artifactory)
2. The mirror is configured in this role because it's the only repo needed to
install conda (no EPEL). No need to put it in the ics-ans-role-repository and
add a dependency.

- only specify the python version to install (without exact dependencies
to avoid deprecated packages)
- use file from the repository to test http url (python27_env.yml) to
not rely on an external repository

RPM released by anaconda.
Installation is done from the RPM to avoid adding the repository as
dependency.

https://docs.ansible.com/ansible/devel/porting_guides/porting_guide_2.7.html#using-a-loop-on-a-package-module-via-squash-actions

Still issue with the new installer:
NotWritableError: The current user does not have write permissions to a required path.\n  path: /home/conda/.conda/pkgs/urls.txt

Update installer as well

Artifactory added native support for conda repository.
The URL should include /api/conda.

JIRA INFRA-604

Dynamic includes and attribute inheritance changed in Ansible 2.5
tags are only applied to the include_* itself and are not inherited by
the tasks within.

See https://docs.ansible.com/ansible/2.5/porting_guides/porting_guide_2.5.html#dynamic-includes-and-attribute-inheritance

By default, if the file exists locally, get_url will NOT download the
file.
force shall be set to true to force the file to be downloaded.

1. Artifactory hosts a mirror of:
- conda-forge
- anaconda-main (this is the only channel from defaults that we care
  about)

We also add the ics-conda channel.
We probably want to allow people to add extra channels in the future.

2. Remove the user condarc file. The default configuration should be
   done at system level.

We want to track the changes to the conda environment files.
They should be in git instead of artifactory.

Use a handler to create the environment

Installer NOT updated to 4.4.10 due to this bug:
https://github.com/conda/conda/issues/7109

Have to wait for a newer installer before to update.
The installer doesn't really matter as long as we can update conda to
the version we want.

Use include_tasks instead of include (requires Ansible 2.4)

The conda env create command (with become) fails when
/home/conda/.conda/environments.txt doesn't exist.

See https://github.com/conda/conda/issues/6576

- update Miniconda installer (required to install conda 4.4)
- pin conda package to defaults channel to avoid downgrade with
  conda-forge channel
- use new /opt/conda/etc/profile.d/conda.sh profile script (remove old
  conda_env.sh)

Note that conda base environment is not activated.

The wheel version that was used was removed (broken package?)

environment files shall be passed via the conda_env_files variable.

Miniconda2 was made the default because of Ansible, but there is no
reason.
Ansible has to use the default Python installation in the first place.

For molecule, there is no problem to install that in a conda env with
Python2.

A new miniconda installer is not released with every conda version.
`conda_version` is now independant of `miniconda_version`.

Add tests on conda user

Ansible still requires Python 2.
We make Miniconda2 the default.

It's still possible to install Miniconda3 by overriding
miniconda_version and miniconda_installer_md5.

sudo is required to install conda.
It's automatically installed by molecule so the missing dependency was
not detected by molecule test.