Add --noIndexRestore to mongorestore options #2
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.
This raises an interesting issue, so please feel free to reject;
--noIndexRestore
is only supported inmongorestore
version 2.2.0 and higher. Adding--noIndexRestore
to the arguments of an older version ofmongorestore
will result in an error.Perhaps
mongoid-shell
could add even more value by providing tool version portability for arguments like this? So if:noIndexRestore
was included among the options toMongoid::Shell::Commands::Mongorestore.new
, the gem could make a decision about whether to actually include it in the command string, based on the version of the underlying tool?