CLOUDP-337612: Update Autogenerated Commands (#4122)

Co-authored-by: apix-bot[bot] <168195273+apix-bot[bot]@users.noreply.github.com>

Author: apix-bot[bot]

docs/command/atlas-api-alerts-listAlerts.txt

@@ -88,7 +88,7 @@ Options
    * - --status
      - string
      - false
-     - Status of the alerts to return. Omit to return all alerts in all statuses.
+     - 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.
    * - --version
      - string
      - false

docs/command/atlas-api-cloudProviderAccess-createCloudProviderAccessRole.txt

@@ -17,7 +17,7 @@ atlas api cloudProviderAccess createCloudProviderAccessRole
 The atlas api sub-command, automatically generated from the MongoDB Atlas Admin API, offers full coverage of the Admin API and is currently in Public Preview (please provide feedback at https://feedback.mongodb.com/forums/930808-atlas-cli).
 Admin API capabilities have their own release lifecycle, which you can check via the provided API endpoint documentation link.
 
-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.
+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.
 
 This command is autogenerated and corresponds 1:1 with the Atlas API endpoint https://www.mongodb.com/docs/api/doc/atlas-admin-api-v2/operation/operation-createcloudprovideraccessrole.
 

docs/command/atlas-api-mongoDbCloudUsers-listTeamUsers.txt

@@ -90,6 +90,10 @@ Options
      - string
      - true
      - Unique 24-hexadecimal digit string that identifies the team whose application users you want to return.
+   * - --userId
+     - string
+     - false
+     - Unique 24-hexadecimal digit string to filter users by. Not supported in deprecated versions.
    * - --username
      - string
      - false

docs/command/atlas-api-rollingIndex.txt

@@ -17,7 +17,7 @@ atlas api rollingIndex
 The atlas api sub-command, automatically generated from the MongoDB Atlas Admin API, offers full coverage of the Admin API and is currently in Public Preview (please provide feedback at https://feedback.mongodb.com/forums/930808-atlas-cli).
 Admin API capabilities have their own release lifecycle, which you can check via the provided API endpoint documentation link.
 
-You can't create a rolling index on an M0 free cluster or M2/M5 shared cluster.
+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.
 
 Options
 -------