Add a --no-update option to sampledata:deploy and sampledata:remove commands #12359
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.
Description
This PR adds a
--no-update
flag for sampledata commands. It will be passed to composer, so that the user can add and remove sampledata modules without automaticcomposer update
. This way, the actual update can be postponed to a manual composer execution. It gives the developer more control and is especially useful in scenarios where running composer from within bin/magento results in permission issues.Manual testing scenarios
First scenario:
bin/magento sampledata:deploy --no-update
on an installation without sampledatacomposer.json
should have been updated, nothing installedSecond scenario:
bin/magento sampledate:remove --no-update
on an installation with sampledatacomposer.json
should have been updated, nothing installedContribution checklist