Atlas CLI
The MongoDB Atlas Command Line Interface, or Atlas CLI (mongodb-atlas-cli), allows you to create, manage, and automate operations related to your MongoDB Atlas deployment. This includes tasks like provisioning clusters, creating and deleting users, and controlling network access. You can also access related products like Atlas Search. With the Atlas CLI, you can quickly interact with MongoDB services from the command line for easier testing and scripting.
To report bugs, please use our mongodbcli github issues.
25 results found
-
New mongodb-atlas-auth Github Action to use OIDC flow for GitHub
As discussed in MongoDB support case 01433340:
When configuring GitHub Actions to manage control plane configurations in public cloud environments (e.g., GCP, Azure, AWS, et cetera), we set up OpenID Connect ("OIDC") to allow the GHA workflows the ability to authenticate with that cloud provider without needing to store credentials as long-lived GitHub secrets (i.e., API keys). Please update and merge to main an official atlas-github-action that allows the option to use of OAuth2 / OIDC (without requiring any API keys).
12 votes -
Update the atlas-github-action to support OAuth2
This item updates the existing MongoDB Atlas Github Action to provide support for OAuth2 authentication flow.
12 votesThank you for voting on this request. Please note that the original request has been split into two components, and this request is now just to support OAuth2 flow. The work to provide this is planned, and we'll provide an update when available.
-
Official Docker Image for Atlas Search
It Could be very useful test Atlas search locally using a dedicated Docker Image, so it is portable to a Kubernetes cluster
9 votesWe now have a docker image that includes the MongoDB server and Atlas Search and Vector Search: https://www.mongodb.com/docs/atlas/cli/current/atlas-cli-deploy-docker/. This image is designed (and licensed for) development and testing locally and in CI/CD. It is not intended for production use.
The image is currently in public preview and we expect to GA it later in the year (2024).
-
Change timeZone for Atlas project via CLI or API
It would be great if there will be the possibility to change timezone for a project via cli or API.
e.g.
curl --user "<PUBLIC_API_KEY>:<PRIVATE_API_KEY>" \
--digest \
--request PATCH "https://cloud.mongodb.com/api/atlas/v1.0/groups/<GROUP_ID>" \
--header "Content-Type: application/json" \
--data '{
"timezone": "Europe/Berlin"
}'Thank you
KR
Norbert6 votes -
Ability to set maxClauseCount for cli image
We have a query that needs to filter by a long list of ids.
I get the error: “Query contains too many nested clauses; maxClauseCount is set to 1024”
This error does not happen in M10+ cluster because the lucene maxClauseCount seems to be higher there.
It would be great to be able to set the maxClauseCount of lucene with an env var so we can test this.
3 votes -
add a command to list and check the invoices
It would be great if there will be the possibility to get information about invoices with atlas-cli like via API.
3 votesThanks for voting on this request to add support for a command to list and check invoices via the Atlas CLI. Great news: the latest version of the Atlas CLI ships with a new Public Preview feature that makes all Atlas Admin API endpoints available, including invoices.
You can now run commands like `atlas api invoices listInvoices` to return invoices for your organization. We're written an overview for using the feature here, and you can read more about the invoices subcommand, as well as other new `api` subcommands in our documentation here.
Please note that the `atlas api` subcommand is a Public Preview feature; we'd love you to try it and to submit your feedback here. Thanks again for your suggestions and votes.
-
Display List of Suggested Indexes to Drop via CLI
Allow users to view the list of suggested indexes to drop via the CLI. Since this functionality is already available in the Atlas UI, it would be beneficial to extend it to the CLI as well. This would align with the existing feature that lists suggested indexes to be created, as documented here (https://www.mongodb.com/docs/atlas/cli/current/command/atlas-performanceAdvisor-suggeste
2 votes -
Option To Return Errors As JSON
Hi,
When using the
--output jsonI would expect the errors to be returned as JSON just like the success output. However, the output for errors seems to continue to be a flat string.It would be helpful from a scripting perspective to have the output as JSON when requested so we can include better logic in our scripts when errors occur. For example:
{ "code": "409", "message": "The cluster name already exists" }Please let me know if you need more information about the request.
Thanks,
2 votesHi Nic,
Thank you for taking the time to raise this request. We'll look into it and update this feedback when we decide to roadmap it for the near future.
Thank you,
Jakub
-
add option to return output as a text instead of array
when you call cli with -o json-path option you always recieve output as an array in brackets. it would be useful to add a key to return output as plain text, so it can used in scripts without further processing (the same way as aws cli does) :
current state :
export org_id=$(atlas organizations list -o json-path='$.results[?(@.name =="MyOrg")].id' )
echo $org_id
[5ccefa1079358eebfef9456e]
suggested output
echo $org_id 5ccefa1079358eebfef9456e2 votes -
list all Atlas Search indexes for a cluster
The list Atlas Search indexes command,
https://www.mongodb.com/docs/atlas/cli/stable/command/atlas-clusters-search-indexes-list/ought to not require the collections and db parameters. It should list indexes for all for the cluster and for a database.
2 votes -
Ability to set mongod configuration parameters at startup
For example, when spinning up a container in CI using mongodb-atlas-local image, be able to set
ttlMonitorEnabled=falsewithsetParameter. The current workaround – spinning up an extra thread to call mongosh --eval 'db.adminCommand({ setParameter:1, ttlMonitorEnabled: false })' some time after the service is healthy – isn't optimal.1 vote -
Update Search Index by Name
It's hard to find a document that clearly states a model to use when creating/updating a Search Index (after digging a little more I found an API documentation that helped me a little but I still had to rely on trial and error).
Update and removal operations should be possible using only the name of the Search Index. This makes it difficult to implement a CI/CD pipeline with Atlas CLI.
1 vote -
Ability to upgrade MongoDB version for local Atlas deployment
Add the ability for the Atlas CLI to upgrade the version of MongoDB running in a local Atlas deployment without having to do a manual migration (or creating a new container).
1 vote -
Add SQL Schema Management to Atlas CLI for Data Federation
Currently, the MongoDB Atlas CLI does not offer commands for managing SQL schemas directly. While the
atlas dataFederationcommand set includes subcommands for managing Data Federation instances, there is no direct support for SQL schema management.It would be highly beneficial if the Atlas CLI included commands for SQL schema management, allowing users to manage their schemas directly through the command line. This would enhance productivity and streamline workflows, particularly for developers who prefer using the CLI for database management.
1 vote -
skip past MongoDB CLI version 1.31.1 for dependabot / renovate (current version 1.18.0)
Currently the latest release for the cli is 1.18 i.e. mongodb/atlas:v1.18.0, but according to common versioning patterns mongodb/atlas:v1.31.0
should have been created after the current version, so vulnerability management systems like renovate will falsely believe this to be the latest version.Could you release versions higher than 1.31.1 from now on?
1 vote -
Token retrival as a API / CLI / endpoint call
When we try to authenticate using Atlas CLI or Administration API, We require to go to shell and need to give approval / confirmation / consent. Would be a great feature to get token as a response of API call / CLI request which will allow seamless integration between the client app and MongoDB Atlas. More use cases will be opened for SaaS, PaaS applications.
1 vote -
atlas clusters sampleData reload
Hi Jakob/Guss/Colm,
Any chance of adding a new command to sampleData - specifically:
atlas clusters sampleData reload <cluster>The command would literally check if the cluster has the sampleData loaded but it would also check the counts and the hashes so that if there wasn't an exact match so the data in some or all of the collections had been changed, then the existing sample data would be dropped and reloaded?
Thanks!
Eoin1 vote -
atlas clusters sampleData loaded command
Hi Jakob/Guss/Colm,
Any chance of adding a new command to sampleData - specifically:
atlas clusters sampleData loaded <cluster>The command would literally check if the cluster has the sampleData present?
I'd find that helpful in some of the lab scripts I'm writing as I'd avoid an unnecessary call to load the sampleData if it was already present. It throws a nasty looking red warning for learners when I do it by default to ensure the data is there.Thanks!
Eoin1 vote -
Add Multi-Factor Authentication settings to be managed via Atlas CLI
At the moment, there is currently no method to manage or view Multi-Factor Authentication settings via the Atlas CLI.
The alerts set in this moment to control MFA seem to be quite poor and it is not possible to get specific information about users.1 vote -
alerts list should allow filtering by date and sort inversely by date
The 'alert list' list all alerts since the beginning of time. We can list open alerts, but we can't practically list alerts that were generated recently without going through all alerts ever produced for a project. I'd like to see what alerts were produced and are open or produce recently but closed.
Additionally, what is a "tracking" alert?
1 vote
- Don't see your idea?