Devon
My feedback
1 result found
-
22 votes
An error occurred while saving the comment Devon
supported this idea
·
We're glad you're here
Please sign in to leave feedback
Signed in as
(Sign out)
We're glad you're here
Please sign in to leave feedback
Signed in as
(Sign out)
Feedback and Knowledge Base
-
Searching…
No results.
Clear search results
-
Give feedback
- Atlas 1,258 ideas
- Atlas App Services 234 ideas
- Atlas CLI 23 ideas
- Atlas Search 149 ideas
- Atlas Stream Processing 1 idea
- Charts 236 ideas
- Compass 393 ideas
- Connectors (BI, Kafka, Spark) 40 ideas
- Data Federation and Data Lake 51 ideas
- Database 272 ideas
- Documentation 6 ideas
- Drivers 67 ideas
- Education 33 ideas
- FLE and Queryable Encryption 3 ideas
- MongoDB Analyzer (for .NET) 1 idea
- MongoDB for VS Code 62 ideas
- MongoDB Shell 36 ideas
- Ops Tools 441 ideas
- Realm 84 ideas
- Relational Migrator 1 idea
- Support Website 13 ideas
- UI 108 ideas
- Vector Search 4 ideas
we use mongosh as part of our application deployment process where we checkout release-specific artifacts from source code control, build a "work file (.js)" of all changes for the release, then execute that script by piping it into the mongosh. We are not able to retrieve commands or return results of the commands indicating success/failure. Instead, we see something like:
Atlas [mongos] test> myDB
Atlas [mongos] myDB> ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ...
Atlas [mongos] myDB> ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ...
Atlas [mongos] myDB> ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ...
Atlas [mongos] myDB> ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ...
Atlas [mongos] myDB>
Atlas [mongos] myDB> ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ...
More control over command capture and result verbosity is critical to determining success/failure of a deployment.