CLOUDP-337612: Update Autogenerated Commands #4122
Open
+588
−801
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![apix-bot[bot]](https://avatars.githubusercontent.com/u/124201131?s=60&v=4){kind=small}
apix-bot
bot
added
auto_close_jira
github-actions
bot
added
need-doc-review
|
APIx Bot |
: a message has been sent to Docs Slack channel 🚀.
|
coverage: 64.472% (-0.007%) from 64.479% |
corryroot
approved these changes
Aug 12, 2025
| @@ -1227,7 +1227,7 @@ For more information and examples, see: https://www.mongodb.com/docs/atlas/cli/c | |||
| }, | |||
| { | |||
| Name: `status`, | |||
| Description: `Status of the alerts to return. Omit to return all alerts in all statuses.`, | |||
| Description: `Status of the alerts to return. Omit this parameter to return all alerts in all statuses. TRACKING indicates the alert condition exists but has not persisted for the minimum notification delay. OPEN indicates the alert condition currently exists. CLOSED indicates the alert condition has been resolved.`, | |||
There was a problem hiding this comment.
Suggested change
| Description: `Status of the alerts to return. Omit this parameter to return all alerts in all statuses. TRACKING indicates the alert condition exists but has not persisted for the minimum notification delay. OPEN indicates the alert condition currently exists. CLOSED indicates the alert condition has been resolved.`, | |
| Description: `Status of the alerts to return. Omit this parameter to return all alerts in all statuses. TRACKING indicates the alert condition exists, but has not persisted for the minimum notification delay. OPEN indicates the alert condition currently exists. CLOSED indicates the alert condition is resolved.`, |
| @@ -6093,7 +6093,7 @@ NOTE: Groups and projects are synonymous terms. Your group id is the same as you | |||
| { | |||
| OperationID: `createCloudProviderAccessRole`, | |||
| Aliases: nil, | |||
| Description: `Creates one access role for the specified cloud provider. Some MongoDB Cloud features use these cloud provider access roles for authentication. To use this resource, the requesting Service Account or API Key must have the Project Owner role. | |||
| Description: `Creates one access role for the specified cloud provider. Some MongoDB Cloud features use these cloud provider access roles for authentication. To use this resource, the requesting Service Account or API Key must have the Project Owner role. For the GCP provider, if the project folder is not yet provisioned, Atlas will now create the role asynchronously. An intermediate role with status IN_PROGRESS will be returned, and the final service account will be provisioned. Once the GCP project is set up, subsequent requests will create the service account synchronously. | |||
There was a problem hiding this comment.
Suggested change
| Description: `Creates one access role for the specified cloud provider. Some MongoDB Cloud features use these cloud provider access roles for authentication. To use this resource, the requesting Service Account or API Key must have the Project Owner role. For the GCP provider, if the project folder is not yet provisioned, Atlas will now create the role asynchronously. An intermediate role with status IN_PROGRESS will be returned, and the final service account will be provisioned. Once the GCP project is set up, subsequent requests will create the service account synchronously. | |
| Description: `Creates one access role for the specified cloud provider. Some MongoDB Cloud features use these cloud provider access roles for authentication. To use this resource, the requesting Service Account or API Key must have the Project Owner role. For the GCP provider, if the project folder isn't provisioned yet, Atlas creates the role asynchronously. An intermediate role with IN_PROGRESS is returned, and the final service account is provisioned. After the GCP project is set up, subsequent requests create the service account synchronously. |
| @@ -28446,7 +28456,7 @@ For more information and examples, see: https://www.mongodb.com/docs/atlas/cli/c | |||
| }, | |||
| { | |||
| Name: `Rolling Index`, | |||
| Description: `Creates one index to a database deployment in a rolling manner. You can't create a rolling index on an M0 free cluster or M2/M5 shared cluster.`, | |||
| Description: `Creates one index to a database deployment in a rolling manner. Rolling indexes build indexes on the applicable nodes sequentially and may reduce the performance impact of an index build if your deployment's average CPU utilization exceeds (N-1)/N-10% where N is the number of CPU threads available to mongod of if the WiredTiger cache fill ratio regularly exceeds 90%. If your deployment does not meet this criteria, use the default index build. You can't create a rolling index on an M0 free cluster or M2/M5 shared cluster.`, | |||
There was a problem hiding this comment.
Suggested change
| Description: `Creates one index to a database deployment in a rolling manner. Rolling indexes build indexes on the applicable nodes sequentially and may reduce the performance impact of an index build if your deployment's average CPU utilization exceeds (N-1)/N-10% where N is the number of CPU threads available to mongod of if the WiredTiger cache fill ratio regularly exceeds 90%. If your deployment does not meet this criteria, use the default index build. You can't create a rolling index on an M0 free cluster or M2/M5 shared cluster.`, | |
| Description: `Creates one index to a database deployment in a rolling manner. Rolling indexes build indexes on the applicable nodes sequentially and might reduce the performance impact of an index build if your deployment's average CPU utilization exceeds (N-1)/N-10% where N is the number of CPU threads available to mongod or if the WiredTiger cache fill ratio regularly exceeds 90%. If your deployment does not meet this criteria, use the default index build. You can't create a rolling index on an M0 free cluster or M2/M5 shared cluster.`, |
| @@ -7923,7 +7855,7 @@ var metadata = metadatatypes.Metadata{ | |||
| Usage: `Flag that indicates whether the response body should be in the prettyprint format.`, | |||
| }, | |||
| `status`: { | |||
| Usage: `Status of the alerts to return. Omit to return all alerts in all statuses.`, | |||
| Usage: `Status of the alerts to return. Omit this parameter to return all alerts in all statuses. TRACKING indicates the alert condition exists but has not persisted for the minimum notification delay. OPEN indicates the alert condition currently exists. CLOSED indicates the alert condition has been resolved.`, | |||
There was a problem hiding this comment.
Suggested change
| Usage: `Status of the alerts to return. Omit this parameter to return all alerts in all statuses. TRACKING indicates the alert condition exists but has not persisted for the minimum notification delay. OPEN indicates the alert condition currently exists. CLOSED indicates the alert condition has been resolved.`, | |
| Usage: `Status of the alerts to return. Omit this parameter to return all alerts in all statuses. TRACKING indicates the alert condition exists, but has not persisted for the minimum notification delay. OPEN indicates the alert condition currently exists. CLOSED indicates the alert condition is resolved.`, |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proposed changes
Update Autogenerated Commands
Jira ticket: CLOUDP-337612
Note: Jira ticket will be closed automatically when this PR is merged.