Why doesn't MongoDB provide a tool (integrated or standalone) to operate document migration across on-prem (sharded) clusters? Suggestion might be to officially support tools like "mongo push", which may cover situations of hardware changes, production servers migration, re-sharding.

Supported Ansible modules for MongoDB. Maybe a module for self managed and Atlas.

It would be ideal if the mongomirror utility could accept SRV-based connection strings for the source and destination clusters. The inability to do this can cause pain for customers. For example, this does not work:

--destination "mongodb+srv://mgo-aura-dgs-prdsrv-tk-pl-0.yrmiy.mongodb.net"

So users are stuck doing this:

--destination "atlas-nkaylx-shard-0/pl-0-ap-northeast-1.yrmiy.mongodb.net:1036,pl-0-ap-northeast-1.yrmiy.mongodb.net:1037,pl-0-ap-northeast-1.yrmiy.mongodb.net:1038"

Two issues with that:
1. It's painful looking up the host/port and atlas defined replica set name
2. The destination info is unreadable by most humans. The service name (i.e. SRV record connstring) includes the name of the cluster that the customer defined, and not the random has that Atlas generates

I went through Mongo spark connector python documentation but the thing which I could not find in python documentation was "MongoSpark Helper" section which is available in scala and java documentation.
I was wondering if there is a way to use it in python code after adding the mongo spark connector packages.

A sample code to demonstrate what is available and what I am looking for (this code is in scala and I am looking for a similar behavior in python)

Code in use:
sparkSession.read.format("mongo").option("uri", "mongodb://dummymongo:27017")

Code looking for:
MongoSpark.builder().connector(connectorwithcustomclientfactory)
.sparkSession(sparkSession).readConfig(dummyReadConfig).build().toDF()

Please add a timeout parameter to the mongocli whitelist command.
Presently, we have to login via web browser to enable temporary mongoshell access from temporary locations.

This will allow other MongoDB components to encrypt credentials with the use of the same Ops Manager credentialstool: https://docs.opsmanager.mongodb.com/current/tutorial/encrypt-user-credentials/index.html

Is it possible to add the support for user roles to the bind api for the Atlas Open Service Broker?

Customers that are currently using the OSB are limited in that they are having to separately manage the creation and assignment of roles.

ตกงาน

Cpanel doesn't have any support for Mongodb

To support chaos engineering.

When running something like "mongoimport --host Cluster0-shard-0/cluster0-shard-00-00-MY.mongodb.net:27017,cluster0-shard-00-01-MY.mongodb.net:27017,cluster0-shard-00-02-MY.mongodb.net:27017 --ssl --username MYUSER --password MYPASS --authenticationDatabase admin --db db --collection coll --type json --file D:\downloads\records.json". You get error "2019-09-28T15:40:34.076-0600 Failed: cannot decode array into a D". You have to use the "--jsonArray". Why wouldn't this be the default. Almost all JSON objects have arrays via mass import/export. Worse case, it should give a better error message.

It would be perfect,

If I have "Credential ID" and "Verification Link" for courses that I have completed.

Yes, I know, MongoDB provides this information for professional certified developer, but

Why not for the certificate of completion?

Currently while using mongocli to connect to Ops Manager via https, one needs to add the public CA certificate to local system's trusted certificate store. Please add a parameter in the configuration file where one can specify the path to the local CA file

In places in the text in different units it says:
"We are connected to the class atlas cluster from Compass".

You could please be explicit with what that address is, since if one is coming back after a couple of days break and have forgotten how to connect to Compass or Mango Shell. If a link to that is provided its a lot faster to be back on track.

Is it possible to add the support for user roles to the bind api for the Atlas Open Service Broker?

Customers that are currently using the OSB are limited in that they are having to separately manage the creation and assignment of roles.