Releases for Acquia Cloud Site Factory Connector

Improved the acsf-uninstall command.

Removed unused code from the module.

• Less files are now being copied and required as part of acsf-init.
• Improved PHP 8.1 compatibility.

 

Various bugfixes and improvements.

• Hashing algorithm has been updated
• The pre-web-activate hook now uses the correct PHP binary.

• Hashing algorithm has been updated
• The pre-web-activate hook now uses the correct PHP binary.

Fixed an issue where the site public file path was not available during site install.

1. Travis CI: ACSF Module travis.yml has been updated to test against PHP 7.3 and PHP 7.4. PHP 7.1 and PHP 7.2 checks were removed.
2. Database scrubbing process done during staging now makes sure the cache table exists before removing its data.

1. Travis CI: ACSF Module travis.yml has been updated to test against PHP 7.3 and PHP 7.4. PHP 7.1 and PHP 7.2 checks were removed.

Database scrubbing process done during staging now makes sure there are no stale caches left.

• Drush 9 and 10 processes now use the correct cache directories for staging process, similar to drush 8 processes.

• updated deprecated Drupal 8 code, to bring the module closer to Drupal 9 readiness. The module now requires Drupal 8.5.0 or higher. A protected object inside the AcsfDuplicationScrubEntityHandler class has changed slightly so anyone extending this class should doublecheck their code.
• added compatibility with Drush 10. Customers should test thoroughly before pushing a codebase to production that includes Drush 10.
• various topics are documented in the readme.md file.

• various topics are documented in the readme.md file.

Snapshot meant only for automated testing - contents are not guaranteed to persist.

- The Acquia Cloud-provided Twig cache directory location is no
longer overridden by the Drupal 8 Acquia Cloud Site Factory Connector
module.
- Several updates have been made to improve future domain resolution.

• Fixed warnings being thrown on a non-ACSF environment when the acsf_sso module is enabled.
• The configuration overrides from sites/g/services.yml is no longer used.
• Installation of the acsf module on a non-ACSF environment will not log a warning anymore.
• Running Drupal cron on a non-ACSF system which has installed the acsf module will not log a warning anymore.
• Changed unit tests to be able to run as part of a larger system as well as the standalone module.

• Installation of the acsf module on a non-ACSF environment will not log a warning anymore.
• Running Drupal cron on a non-ACSF system which has installed the acsf module will not log a warning anymore.
• Changed unit tests to be able to run as part of a larger system as well as the standalone module.

Database lookups for domain names are now cached in APCu.

- Some drush commands that do not target a specific site (e.g. 'drush status') would emit notices about the DRUPAL_ROOT constant not existing.
- Some fixes were made to the consistency of how the 'sjadd' command is run to add scheduled jobs. No exceptions are thrown anymore.

- Some drush commands that do not target a specific site (e.g. 'drush status') would emit notices about the DRUPAL_ROOT constant not existing.
- Some fixes were made to the consistency of how the 'sjadd' command is run to add scheduled jobs. No exceptions are thrown anymore.

- All submodules have their own composer.json now, which should make https://packages.drupal.org publish the correct (PHP7.2 compatible) dependencies for the acsf_sso module.
- The cloud hooks (pre-web-activate, post-db-copy) no longer assume they are installed on ACSF environments; this means the module can be installed without adverse affects on ACE.

The cloud hooks (pre-web-activate, post-db-copy) no longer assume they are installed on ACSF environments; this means the module can be installed without adverse affects on ACE.