Add ability to set custom MySQL ports

This release adds ability to configure magento with custom mysql ports, this is optional and backwards compatible

To use custom port set:

magento_config_db:
    ...
    port = [custom port number]

and

magento_db_connections:
  - type: "connection"
    databases:
        ...
        host: "[mysql host]:[custom port number]"

4.3.0: Merge pull request #19 from sitewards/ADHOC-modernize-a-bit

Minor modernization improvements

Redis is now referenced according to magento docs recommendations:

• magento_cache_frontend_page_cache_backend: "\Magento\Framework\Cache\Backend\Redis"

Add Asynchronous operations

Improve deployment performance by utilizing asynchronous completion of old clones cleanup and magento reindexing after deploy

The two new features can be activated by setting:

• magento_allow_async_reindex: true
• magento_allow_async_cleanup_old_clones: true

Both are set to false by default for backwards compatibility

Configurable wait for consumer messages

Features:

• optional setting to stop waiting for message consumers magento_queue_consumers_wait_for_messages

This feature was meant to be released in the previous major version but was excluded by accident
By default it is set to false, existing projects will therefore see no change unless this variable is defined in the
project and set to true

Breaking changes for redis page cache backends

Features

• optional setting to stop waiting for message consumers
• required forced expiry for redis cache entries
• required compression lib setting for redis cache

Breaking Changes

When magento_cache_frontend_page_cache_backend and/or magento_cache_frontend_default_backend are set to Cm_Cache_Backend_Redis several new settings for forced expiry of entries and compression library are now required.

Fix symlinking error while deployment

It was discovered that deployment was failing while the server was under
load. The reason was, that magento was recreating the shared folders
between the deletion and the symlinking.

We move this step now to be done before the symlink is moved to the new
magento deployed folder. This is also saving some downtime in the
deployment.

*#####################
*## Breaking Change ##
*#####################

This includes a backwards incompatible change. As the targets for the
shared folders needs now to be defined relative to the application root
folder. Absolute pathes are not possible anymore.

So you want to change your config something like this

 magento_shared_folders:
   - src: "{{ magento_shared_directory }}/pub/media"
-    dest: "{{ magento_app_root }}/pub/media"
+    dest: "pub/media"

Add sap credentials, additional config and log rotation

This features where required in one of our projects. It's helps preventing from disks filling up and gives more flexibility in configuration.

Better deploy performance

Changed the way how file permissions are controlled during the deploy,
this should speed up deployment routines by some minutes.

One single ansible steps was taking 5-10 minutes (or even 40, depending
on the amount of files) to complete, with this change it takes few seconds.
So deployment generally becomes faster overall.

Indexer run on deployment

With this release an opportunity to run a complete reindex upon deployment is added.

2.1.0 Automatic clone cleanup

Major feature added - automatic cleanup of old clones to keep the disk usage under control.