ACSD-64532: ENV variable set to false is treated as a string false instead of a BOOLEAN FALSE

Categories

Other

Components

magento/framework

Origin

adobe-commerce-support

Since QPT

1.1.62

Issue

ENV variable set to false is treated as a string false instead of a BOOLEAN FALSE.

Steps to reproduce

1. Add env:MAGENTO_DC_INDEXER__USE_APPLICATION_LOCK with value false to environment variables on Adobe Commerce on cloud infrastructure. 1. Wait for redeployment. 1. Run the script checking the value: <?php require '../app/bootstrap.php'; $bootstrap = \Magento\Framework\App\Bootstrap::create(BP, $_SERVER); $objectManager = $bootstrap->getObjectManager(); $deploymentConfig = $objectManager->get('Magento\Framework\App\DeploymentConfig'); $useAppLock = $deploymentConfig->get('indexer/use_application_lock'); var_dump($useAppLock); $configParsedValue = $deploymentConfig->get('indexer/use_application_lock') ?: false; var_dump($configParsedValue);

Adobe's page lists 2.4.6-p2 - 2.4.7-p4 as compatible; the versions below are resolved from the current QPT constraints and are the ones the tool will offer.

Adobe scheduled the permanent fix for 2.4.8.

Install

Install the Quality Patches Tool with composer require magento/quality-patches, apply the prerequisites listed for all files applicable to your distribution and version first, then run vendor/bin/magento-patches apply ACSD-64532. On Cloud, add ACSD-64532 under stage.build.QUALITY_PATCHES in .magento.env.yaml.

For cweagans/composer-patches, choose a compatible version below and download the bundle. Copy its ACSD-64532/ folder into patches/composer/, merge composer.patches.json into composer.json, then run composer install. Bundle prerequisites the same way and list them first. Paths are relative to each package root, using the default -p1 level. Prefer local files when configuring composer-patches; a remote URL can change.

Patch files and compatible versions

Sources

• Adobe documentation for ACSD-64532
• JSON API: /api/v1/patches/ACSD-64532