I have two migrations, image and media, and media depends on image.
If I explicitly request to run both of them in one order it's fine:
$ drush mim image,media --execute-dependencies --update
[notice] Processed 1 item (0 created, 1 updated, 0 failed, 0 ignored) - done with 'image'
[notice] Processed 1 item (0 created, 1 updated, 0 failed, 0 ignored) - done with 'media'
but if I swap the order, the image migration is run twice:
$ drush mim media,image --execute-dependencies --update
[notice] Processed 1 item (0 created, 1 updated, 0 failed, 0 ignored) - done with 'image'
[notice] Processed 1 item (0 created, 1 updated, 0 failed, 0 ignored) - done with 'media'
[notice] Processed 1 item (0 created, 1 updated, 0 failed, 0 ignored) - done with 'image'
The order should not matter when --execute-dependencies is specified, the resolution should be the same and image should only be run once.
Active
6.0
Drush commands
I would say the order should/could still matter, just without any migration being run multiple times.
This could be useful if we have a migration X that depends on several other migrations A, B and C. If we know that A and B take particularly long, then we might want to run influence the order and run C first.
There could be other reasons we'd want a migration to run before others aside from explicitly being a "dependency".