Cannot change search engine in app/etc/env.php
This article provides a solution to the issue where you try to remove the search engine configuration from the app/etc/env.php file, but after redeployment, the configuration reverts to the previous setting or is changed to OpenSearch by default.
Affected products and versions
- Adobe Commerce on cloud infrastructure, all supported versions
Issue
You try to change the search engine in the Commerce Admin, but the fields are locked.
Cause
The search engine configuration is locked in the app/etc/env.php file, or the search engine is explicitly defined in the .magento.env.yaml file.
Solution
-
Check the
.magento.env.yamlfile under the deploy stage and see whether theSEARCH_CONFIGURATIONvariable has been configured. Example:SEARCH_CONFIGURATION: engine: elasticsearch7 ... <VARIABLE X> -
Is the
SEARCH_CONFIGURATIONvariable present? If not present, the search engine configuration is locked to OpenSearch by default. To change the configuration, you must add the variable to the.magento.env.yamlfile with the appropriate value for the search engine. If theSEARCH_CONFIGURATIONvariable is present and you wish to modify the engine, replace the existing value for the engine in.magento.env.yaml. Possible/known values: opensearch, livesearch, elasticsuite, amasty_elastic, and amasty_elastic_opensearch. -
Redeploy the instance.
-
The search engine field in the Admin will remain locked, but it should get updated with the value you have specified.
Related reading
- Locked (grayed out) fields in Commerce Admin in Commerce on Cloud Infrastructure Guide.