Make pm:install
and pm:uninstall
respect --simulate
option
#5152
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In Drush 8 it was possible to pass
--no
topm:uninstall
to let it output only what modules would be uninstalled without actually uninstalling any modules. This was removed in Drush 9 after discussion in #205 (PR #1057 was declined as a result).However, we had some automation that used this to see what would be uninstalled so that this could be reported for user verification, even in the case only a single module would be uninstalled. This is now broken and that command uninstalls the module when it's the only one being uninstalled.
To preserve the new desired behaviour but still easily allow automation to determine what changes would be made by running
pm:install
orpm:uninstall
this PR adds a--dry-run
option that will not actually perform any of the changes.An alternative implementation would be to provide entirely separate commands, but that feels like overkill.