Closed ebeigarts closed 6 years ago
I was just about to start this one. Thank you ebeigarts!
Any idea when this will be rolled out?
Mind rebasing this onto master, @ebeigarts ? Ideally we don't have so many unrelated changes in a single PR.
@josegonzalez rebase done
This breaks usage of older versions of mongodb for import/export. Do we think that is fine to do?
yes, it brakes, but this is more standardized way of exporting/importing. maybe we can add some post-install notes or warning in readme about backwards incompatible changes? and bump version to 1.1.0?
Everything should be fine for users running mongo 3.2+, for users running 3.0, they would need to first upgrade containers running 3.0 to 3.2, and then update the plugin, because the new export needs 3.2+
Agreed with @ebeigarts comments. This makes usage much more standard. Bumping the version number and some release notes should cover it.
@josegonzalez still looking for this. Can you give me write access and ill take over?
Closed by #93.
Fixes tests on OS X by using gnu readlinemongo:export
uses--archive --gzip
(requires mongo 3.2+)mongo:export
silences STDERR since STDERR is converted to STDOUT when usingssh -t
, also other*:export
plugins are silent.mongo:import
uses--archive --gzip --nsFrom ... --nsTo ...
(requires mongo 3.4+)Fixes #70, #84.
I have tested import/export directly on the server and also through ssh -t. it works.