Custom Config File Path

The only way to define a custom config files is by providing a full path or magento/data-migration-tool module install relative path:

https://github.com/magento/data-migration-tool/blob/3c7f83b8eaab690734113f574a26595e61415b62/src/Migration/Reader/Map.php#L83-L84

https://github.com/magento/data-migration-tool/blob/3c7f83b8eaab690734113f574a26595e61415b62/src/Migration/Reader/Settings.php#L96-L98

1. This contradicts the Docs that Claims you can use Magento install relative path:

• https://devdocs.magento.com/guides/v2.3/migration/migration-tool-configure.html#migration-config

The changes here go against what @victor-v-rad said in a similar config issue:

Yes, not only file name should be changed in config.xml file but path also. The only thing is file path can be relative to Data Migration Tool directory or full path. It wont work if you set relative the Magento install directory in <map_file> option in config.xml file. So would suggest to change the text to something like "Change the file path and name in the <options> node in the config.xml file to the new file path and name accordingly"

https://github.com/magento/devdocs/pull/6732#pullrequestreview-365807119

Related:

• https://github.com/magento/devdocs/pull/6775
• https://github.com/magento/data-migration-tool/issues/757

It would help to be able to define a custom config file relative to the Magento install path. I'm working within a cloud environment and the full path changes based on the environment.

Start by reading src/Migration/Reader/Map.php around lines 83-84 and src/Migration/Reader/Settings.php around lines 96-98, then compare their path handling with the linked migration configuration documentation. The work is done when a custom config path can be specified relative to the Magento installation as described, without requiring an environment-specific full path.