Using Env.php to Override Module Status in Config.php

Question

What I am trying to achieve is overriding specific modules declared as enabled in the app/etc/config.php to be disabled by the app/etc/env.php file.

A use case of that would be the 2FA module which I prefer to keep as disabled in the development environments.

I tried adding the module to the env.php file as follows, but the config.php gets updated to 0 as well:

<?php
return [
    'modules' => [
        'Magento_TwoFactorAuth' => 0,
        'Vendor_DevModuleWhichShallNotBeTrackedByTheConfigFile' => 0
    ],
    ...
];

What would be the best practice for this situation? Should I remove the module from the config.php entirely and add it to each server env.php file separately?

Answer 1

You can not enable/disable the module using env.php file, you have two options here:

1. Disable modules config (using config path) in env.php
2. Keep the 2FA modules enabled in config.php and disable the modules during the deployment in your CI process using:

bin/magento module:disable MODULE_NAME