We currently use the restore snapshot job to copy our data to our analytics cluster daily through the Atlas API. We want other databases in our analytics cluster to persist throughout these daily copies (hence why copying and deleting the data afterwards is not sufficient).
A manual dump and restore is currently our only option however it's significantly more expensive (cost and implementation time) as we must use a VM as a middleman for the dump and restore commands.
I'd add that if/when this feature gets implemented, the API should be extended so that this feature can be used in a automated pipeline.
This is a key feature for us.
We currently use the restore snapshot job to copy our data to our analytics cluster daily through the Atlas API. We want other databases in our analytics cluster to persist throughout these daily copies (hence why copying and deleting the data afterwards is not sufficient).
A manual dump and restore is currently our only option however it's significantly more expensive (cost and implementation time) as we must use a VM as a middleman for the dump and restore commands.
I'd add that if/when this feature gets implemented, the API should be extended so that this feature can be used in a automated pipeline.