Pass the mongosh password inline instead of a bare -p

[GuanzhouSong]

A cold-start test that followed this page verbatim in a container failed on the connect step with an error that names neither authentication nor the real cause:

MongoServerError: Invalid key

Cause

The page shows:

mongosh localhost:10260 -u admin -p --authenticationMechanism SCRAM-SHA-256 ...

A bare -p makes mongosh prompt for the password. In a non-interactive shell there is nothing to type, so it sends an empty password. The resulting Invalid key gives no hint that it was an auth failure, let alone an empty-credential one.

This matters here because the page explicitly caters to scripted and container use — it already tells the reader to drop sudo in a container and to export DEBIAN_FRONTEND=noninteractive. Someone following it in exactly that context is the person most likely to hit this.

Fix

Show the inline form, and say why:

mongosh localhost:10260 -u admin -p '<PASSWORD>' --authenticationMechanism SCRAM-SHA-256 \
        --tls --tlsAllowInvalidCertificates --eval 'db.runCommand({ping: 1})'

Verification

Against a live install (packages from the repository, documentdb-setup run, gateway up):

Form	Result
bare -p, non-TTY	exit 1 — MongoServerError: Invalid key
-p '<PASSWORD>' inline	exit 0 — { ok: 1 }

insertOne / find then round-tripped normally.

Related

The same trap exists in the documentdb.io article and is fixed there alongside several air-gapped install blockers found by the same test run: documentdb/documentdb.github.io (PR linked once opened).

Full disclosure: this line is my own from #69 — I promoted the credential-flag form ahead of the URI form to avoid percent-encoding, and traded a visible trap for a quieter one.