Hello @Crtl,
Please check below example, How I override it.
New Company\Performance\Setup\FilePermissions class extends existing Magento\Framework\Setup\FilePermissions class and overrides getInstallationWritableDirectories() method. In this method we are going to check whether path of the directory which should be writable is a symlink or real. In case it is a symlink, we suppose it is an EFS storage and we simply exclude the directory from further recursive is_writable() check.
Assuming that’s only Media directory is stored under EFS we are going to skip only 1 out of 4 directories. The static files however, can also be placed under EFS, but I won’t recommend doing this.
Here is our Company\Performance\Setup\FilePermissions class.
namespace Pronko\Performance\Setup;
use Magento\Framework\Setup\FilePermissions as MagentoFilePermissions;
class FilePermissions extends MagentoFilePermissions
{
/**
* Retrieve list of required writable directories for installation
* Exclude symlinks from isWritable recursive checks
*
* @return array
*/
public function getInstallationWritableDirectories()
{
parent::getInstallationWritableDirectories();
foreach ($this->installationWritableDirectories as $code => $path) {
if (is_link($path)) {
unset($this->installationWritableDirectories[$code]);
}
}
return $this->installationCurrentWritableDirectories;
}
}Next step is to add a preference for our the Magento\Framework\Setup\FilePermissions in di configuration. Since setup code is a different application with Symphony configuration, there is no way we can simply use our own di.xml configuration file to add preference as we always do. Having said, we have to modify <magento_root>/setup/config/di.config.php file and add our new preference:
return [
'di' => [
'instance' => [
'preference' => [
'Magento\Framework\Setup\FilePermissions' => 'Company\Performance\Setup\FilePermissions'
],
],
],
];
*There are other references listed in the original file, which I excluded here in the example.
Also, we have to modify additional configuration file which stores aliases for Setup Application. Remember, we are talking about Symphony application – Setup. Here are changes to the <magento_root>/setup/config/application.config.php file.
use Magento\Setup\Mvc\Bootstrap\InitParamListener;
return [
'modules' => [
'Magento\Setup',
],
'module_listener_options' => [
'module_paths' => [
__DIR__ . '/../src',
],
'config_glob_paths' => [
__DIR__ . '/autoload/{,*.}{global,local}.php',
],
],
'listeners' => [
'Magento\Setup\Mvc\Bootstrap\InitParamListener'
],
'service_manager' => [
'factories' => [
InitParamListener::BOOTSTRAP_PARAM => 'Magento\Setup\Mvc\Bootstrap\InitParamListener'
],
'aliases' => [
'magentoframeworksetupfilepermissions' => 'Company\Performance\Setup\FilePermissions',
]
],
];
Next time you will run bin/magento setup:upgrade command your new version of the code as well as database will be updated almost instantly. Magento won’t be checking permissions of the pub/media directory which is in reality a symlink to a location stored in Elastic File System storage.
--
If my answer is useful, please Accept as Solution & give Kudos
