Warden 0.5.2

Enhancements:

• Fixed inability to run warden debug -c '<command>' in like manner to warden shell -c ...
• Fixed issue where GTID related SET statements in a database dump failed the import (issue #162)

Warden 0.5.1

Upgrade Notes:

All docker images have been re-located to a new Docker Hub organization created specifically for use with Warden. All built-in environment types having been updated to reference the images on docker.io/wardenenv rather than quay.io/warden. Images currently on Quay will remain available (for at least the next 90-days) in order to preserve functionality of Warden prior to the 0.5.1 release, but these will no longer be updated and are considered deprecated immediately. Where references to quay.io/warden exist in per-project configuration within the .warden directory, it is strongly recommended these references be updated to use images from docker.io/wardenenv. You can quickly check an environment's configuration for references to images on Quay via the following command:

warden env config | grep quay.io

The backstory, and reason for moving the images, is that in Warden 0.2.0 (circa January 2020) images were relocated from a single Docker Hub repository to individual repositories on Quay.io both as a means of breaking down a mon-repo and also to leverage images scanning of Quay.io. Since that time, Quay.io has had multiple outages, including a recent one which lasted for 19 hours with intermittent inability to pull images as even read-only operations were failing as the service failed to be scaled. This morning Quay.io is down yet again, prompting all-out inability to pull images. Given the saddening instability of Quay.io and the inability to setup a local mirror as you can with Docker Hub it has become painstakingly obvious that the images must be moved back to Docker Hub for a long-term and stable home, with the added benefit that you will now be able to use a local registry service as a pass-through mirror for reducing network bandwidth and/or ensuring you have a copy of all images local to your network should at any time Docker Hub encounter issues in the future.

The new long-term home for Warden docker images can be found here at https://hub.docker.com/u/wardenenv.

Change Summary:

• Updated images to reside in the docker.io/wardenenv registry on Docker Hub
• Removed usages of images previously on quay.io/warden
• Deprecated images on quay.io/warden for planned removal at some point in the future (to be not less than 90-days from today)

Warden 0.5.0

Upgrade Notes:

If PHP_VERSION is not defined in a project's .env type the default version is now 7.3 across the board for all environment types. This should not pose any issues for recent magento1 or magento2 setups, but laravel environments will likely require an update to the project's .env to continue using PHP 7.2 or rather than 7.3 for local development.

There is a breaking change where custom environment config specific to Linux has been used in the form of placing a .warden/warden-env.linux-gnu.yml file in the project directory. The value used for WARDEN_ENV_SUBT on Linux is now linux rather than linux-gnu. After upgrading, these files will need to be re-named from .warden/warden-env.linux-gnu.yml to .warden/warden-env.linux.yml. Where continued compatibility with prior versions of Warden is desired (for example, to not require the entire team to upgrade Warden at once), a symlink may be placed to point the old file name to the new one allowing Warden to load the definition correctly on both new and old implementations: warden-env.linux-gnu.yml -> warden-env.linux.yml

The BYPASS_VARNISH flag will continue to work as before but has been deprecated to be removed in a future release. It will no longer be included in the .env file created for new magento2 environments.Please use the new feature toggle WARDEN_VARNISH=0 to disable Varnish instead.

Enhancements:

• Added symfony environment type for use with Symfony 4+ (#146 by @lbajsarowicz)
• Added COMPOSER_MEMORY_LIMIT=-1 to env on all php-* containers (#154 by @navarr)
• Added new feature flag WARDEN_DB to enable/disable service on per-project basis.
• Added new feature flag WARDEN_ELASTICSEARCH to enable/disable service on per-project basis.
• Added new feature flag WARDEN_VARNISH to enable/disable service on per-project basis.
• Added new feature flag WARDEN_RABBITMQ to enable/disable service on per-project basis.
• Added new feature flag WARDEN_REDIS to enable/disable service on per-project basis.
• Added new feature flag WARDEN_MAILHOG to enable/disable service on per-project basis.
• Updated WARDEN_ALLURE to now enable Allure container on any environment type.
• Updated WARDEN_SELENIUM to now enable Selenium containers on any environment type.
• Updated WARDEN_BLACKFIRE to now enable Blackfire containers on any environment type.
• Updated env-init command to include locked values for MARIADB_VERSION, NODE_VERSION, PHP_VERSION, and REDIS_VERSION for laravel environment types.
• Updated local env type so it can now include common services by adding the above feature flags to the project .env file.

Warden 0.4.4

Enhancements:

• Updated php-fpm images to use fpm-loaders variant of base image to include IonCube & SourceGuardian from upstream images
• Updated php-fpm images fix for directory ownership of mounted volume paths for future flexibility by moving it to the docker-entrypoint script with an env var CHOWN_DIR_LIST to specify what directories to chown on container startup

Bug Fixes:

• Fixed missing SSH agent forwarding in php-blackfire container
• Fixed lack of extra_hosts in php-blackfire and blackfire-agent containers (issue #145)
• Fixed missing extra_hosts line for non-subdomain entry in /etc/hosts on selenium container
• Fixed $OSTYPE check for compatibility with OpenSUSE which uses linux rather than linux-gnu (#149 by @Den4ik)

Warden 0.4.3

Enhancements:

• Updated init routine allowing WARDEN_HOME_DIR and WARDEN_COMPOSER_DIR to be overriden via environment variables
• Updated environment configuration to reference WARDEN_SSL_DIR eliminating hard-coded ~/.warden/ssl references
• Updated warden global docker config to reference WARDEN_HOME_DIR eliminating hard-coded ~/.warden references
• Updated warden up to return an error when docker is not running rather than blindly attempt to start global services

Warden 0.4.2

Enhancements:

• Added WARDEN_SYNC_IGNORE to support passing a comma-separated list of additional per-session-ignores to Mutagen when sync sessions are started (#142 by @davidalger)
• Added pause, resume and monitor to warden sync command (#141 by @fooman)
• Changed Mutagen sync to pause on warden env stop and resume on warden env up -d (#141 by @fooman)

Bug Fixes:

• Removed exclusion of (commonly large) files types (*.sql, *.gz, *.zip, *.bz2) from sync sessions (as introduced in 0.4.0) because it broke the ability to use artifact repositories with composer (#142 by @davidalger)

Warden 0.4.1

Bug Fixes:

• Removed tmpfs volumes from sub-directories of /var/www/html when WARDEN_TEST_DB=1 was set due to compatibility issues (#139 by @lbajsarowicz)

Warden 0.4.0

Upgrade Notes:

The introduction of SSH Agent Forwarding support in PR #121 results in Warden now requiring Docker Desktop 2.2.0.0 or later for macOS clients. Please upgrade Docker Desktop prior to upgrading to the latest Warden release to avoid errors relating to unauthorized mounts.

Enhancements:

• Added MySQL 5.6 and 5.7 images to Quay repository for use with Warden environments
• Added support for Integration, Unit and API Tests leveraging a MySQL 5.7 container running on tempfs memory disk (#115 by @lbajsarowicz)
• Added WARDEN_ALLURE setting to control Allure separately from Selenium for use reporting on Integration and Unit tests (#117 by @lbajsarowicz)
• Added ssh agent forwarding support on both macOS and Linux hosts (#121 by @davidalger)
• Updated entrypoint in php-fpm images to support mounting PEM files into /etc/pki/ca-trust/source/anchors (3a841b7d)
• Updated config for Mutagen sync to exclude large files (*.sql, *.gz, *.zip, *.bz2) from sync sessions

Bug Fixes:

• Fixed issue where - in WARDEN_ENV_NAME would results in 0.0.0.0 being used in extra_hosts passed to containers
• Fixed race condition caused by docker-compose starting two containers with identical mounts simultaneously (issue #110)
• Fixed issue with incorrect network name reference when uppercase characters are present in WARDEN_ENV_NAME (issue #127)
• Fixed issue where Mutagen sync autostart would attempt to start when php-fpm container was not running (ex: when executing warden env up -d db to start only the db service)

Warden 0.3.1

Upgrade Notes:

If you're upgrading from version 0.2.x to 0.3.x for the first time, please reference upgrade notes for Warden 0.3.0 and plan accordingly.

Bug Fixes:

• Fixed issue where env up and env start would exit with an error on env types not using Mutagen sessions
• Fixed issue where env down and env stop would exit with an error on env types not using Mutagen sessions

Warden 0.3.0

Upgrade Notes:

The fix for issue #65 required removing the warden network from each environment's services (see commit 36cb0174) and as a result environments referencing the warden network in per-project .warden/*.yml configuration files may need to be updated for compatibility with Warden 0.3.0.

Should you see an error like the following when running warden env ... then this applies to you:

ERROR: Service "nginx" uses an undefined network "warden"

To resolve this issue, simply remove the following from each service defined in .warden/*.yml files on the project similar to what was done in commit 36cb0174 on the base environment definitions:

networks:
  - warden
  - default

Bug Fixes:

• Updated to no longer connect environment containers to warden network and instead peer traefik and tunnel containers with each project when it is started (issue #65)

Enhancements:

• Added automatic start of Mutagen sync on env up and env start when sync is not connected (issue #90)
• Added automatic stop of Mutagen sync on env down and env stop (issue #90)
• Updated routing rules so Traefik will now by default route both example.com and *.example.com to application (#111 by davidalger)