Closed wimleers closed 12 months ago
Patch and project coverage have no change.
Comparison is base (
b2c6811
) 91.76% compared to head (f81ded3
) 91.76%.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
Motivation For historical reasons, the predecessor of
acli app:new:from:drupal7
had to hardcode the package containing the AM:A Drupal module.That is still there. It's never gotten in the way.
Until now.
Because
config/from_d7_config.json
is hardcoded to listacquia/acquia-migrate-accelerate
in its project template, the recommendations that we will have at https://git.drupalcode.org/project/acquia_migrate/-/tree/recommendations will generate a project that continues to install the packagist/closed source AMA retrieved from GitHub instead of the open source AMA source retrieved from d.o’s packagist facade.IOW, both of these will exist in the generated
composer.json
:acquia/acquia-migrate-accelerate
drupal/acquia_migrate
(once it exists)Clearly we shouldn't install the same module twice.
Proposed changes Remove
acquia/acquia-migrate-accelerate
from the template.Alternatives considered /
Testing steps If the integration test still passes (which it will 👍 ), you'll know it's working correctly: because
config/from_d7_recommendations.json
is now the only place whereacquia/acquia-migrate-accelerate
is explicitly defined!