Currently, PHP.ini customizations do not appear in SSH sessions or Cloud Hooks without utilizing work-around through .drushrc in the home directory. On Monday, 11 December 2017, Acquia will be implementing a platform improvement that will ensure these customizations are reflected in SSH sessions or Cloud Hooks.
For customers who have a hard-coded path to PHP in their application, this change will likely impact your application's functionality. Additionally, this change may not be compatible with the extensions in your application environments' php.ini.
To bypass the inclusion of your environments php.ini, you can either unset or set to empty string the PHPRC environment variable via the following:
$ php -i | grep 'Loaded Configuration File' Loaded Configuration File => /mnt/www/site-php/mydrupalapp/php.ini
Bypass site php.ini
$ PHPRC="" php -i | grep 'Loaded Configuration File' Loaded Configuration File => /usr/local/php5.6/etc/cli/php.ini
Customers with applications containing hard-coded PHP paths have until 11 December 2017 to update their application code to avoid service interruptions. You can correct your application by simply calling to PHP, without calling to a specific version path, in your application.
Customers should review their application code to determine if your application will be affected. Customers whose applications continue to include hard-coded PHP paths as of 11 December 2017 will encounter service interruptions and application functionality failures if changes are not completed by that time.