Project import generated by Copybara. (#952)

GitOrigin-RevId: 482d470e9fd420401c4f90bf04203b4f96df20b5

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

Author: apix-bot[bot]

source/command/atlas-alerts-settings-create.txt

@@ -52,7 +52,7 @@ Options
    * - -f, --file
      - string
      - false
-     - Path to the JSON configuration file that defines alert configuration settings. To learn more about alert configuration files for the Atlas CLI, see https://dochub.mongodb.org/core/alert-config-atlas-cli.
+     - Path to the JSON configuration file that defines alert configuration settings. Note: Unsupported fields in the JSON file are ignored. To learn more about alert configuration files for the Atlas CLI, see https://dochub.mongodb.org/core/alert-config-atlas-cli.
    * - -h, --help
      - 
      - false

source/command/atlas-alerts-settings-update.txt

@@ -68,7 +68,7 @@ Options
    * - -f, --file
      - string
      - false
-     - Path to the JSON configuration file that defines alert configuration settings. To learn more about alert configuration files for the Atlas CLI, see https://dochub.mongodb.org/core/alert-config-atlas-cli.
+     - Path to the JSON configuration file that defines alert configuration settings. Note: Unsupported fields in the JSON file are ignored. To learn more about alert configuration files for the Atlas CLI, see https://dochub.mongodb.org/core/alert-config-atlas-cli.
    * - -h, --help
      - 
      - false

source/command/atlas-api-accessTracking-listAccessLogsByClusterName.txt

@@ -14,7 +14,11 @@ atlas api accessTracking listAccessLogsByClusterName
 
 `experimental <https://www.mongodb.com/docs/atlas/cli/current/command/atlas-api/>`_: Returns the access logs of one cluster identified by the cluster's name.
 
-Access logs contain a list of authentication requests made against your cluster. You can't use this feature on tenant-tier clusters (M0, M2, M5). To use this resource, the requesting API Key must have the Project Monitoring Admin role. This command is invoking the endpoint with OperationID: 'listAccessLogsByClusterName'. For more information about flags, format of --file and examples, see: https://www.mongodb.com/docs/atlas/reference/api-resources-spec/v2/#tag/Access-Tracking/operation/listAccessLogsByClusterName
+Access logs contain a list of authentication requests made against your cluster. You can't use this feature on tenant-tier clusters (M0, M2, M5). To use this resource, the requesting API Key must have the Project Monitoring Admin role or the Project Database Access Admin role.
+
+This command is autogenerated and corresponds 1:1 with the Atlas API endpoint https://www.mongodb.com/docs/atlas/reference/api-resources-spec/v2/#tag/Access-Tracking/operation/listAccessLogsByClusterName.
+
+For more information and examples, see the referenced API documentation linked above.
 
 Syntax
 ------

source/command/atlas-api-accessTracking-listAccessLogsByHostname.txt

@@ -14,7 +14,11 @@ atlas api accessTracking listAccessLogsByHostname
 
 `experimental <https://www.mongodb.com/docs/atlas/cli/current/command/atlas-api/>`_: Returns the access logs of one cluster identified by the cluster's hostname.
 
-Access logs contain a list of authentication requests made against your clusters. You can't use this feature on tenant-tier clusters (M0, M2, M5). To use this resource, the requesting API Key must have the Project Monitoring Admin role. This command is invoking the endpoint with OperationID: 'listAccessLogsByHostname'. For more information about flags, format of --file and examples, see: https://www.mongodb.com/docs/atlas/reference/api-resources-spec/v2/#tag/Access-Tracking/operation/listAccessLogsByHostname
+Access logs contain a list of authentication requests made against your clusters. You can't use this feature on tenant-tier clusters (M0, M2, M5). To use this resource, the requesting API Key must have the Project Monitoring Admin role or the Project Database Access Admin role.
+
+This command is autogenerated and corresponds 1:1 with the Atlas API endpoint https://www.mongodb.com/docs/atlas/reference/api-resources-spec/v2/#tag/Access-Tracking/operation/listAccessLogsByHostname.
+
+For more information and examples, see the referenced API documentation linked above.
 
 Syntax
 ------

source/command/atlas-api-alertConfigurations-createAlertConfiguration.txt

@@ -14,7 +14,14 @@ atlas api alertConfigurations createAlertConfiguration
 
 `experimental <https://www.mongodb.com/docs/atlas/cli/current/command/atlas-api/>`_: Creates one alert configuration for the specified project.
 
-Alert configurations define the triggers and notification methods for alerts. To use this resource, the requesting API Key must have the Organization Owner or Project Owner role. This resource remains under revision and may change. This command is invoking the endpoint with OperationID: 'createAlertConfiguration'. For more information about flags, format of --file and examples, see: https://www.mongodb.com/docs/atlas/reference/api-resources-spec/v2/#tag/Alert-Configurations/operation/createAlertConfiguration
+Alert configurations define the triggers and notification methods for alerts. To use this resource, the requesting API Key must have the Organization Owner or Project Owner role.
+
+
+This resource remains under revision and may change.
+
+This command is autogenerated and corresponds 1:1 with the Atlas API endpoint https://www.mongodb.com/docs/atlas/reference/api-resources-spec/v2/#tag/Alert-Configurations/operation/createAlertConfiguration.
+
+For more information and examples, see the referenced API documentation linked above.
 
 Syntax
 ------
@@ -44,7 +51,7 @@ Options
    * - --file
      - string
      - false
-     - path to the file which contains the api request contents
+     - path to your API request file. Leave empty to use standard input instead - you must provide one or the other, but not both.
    * - --groupId
      - string
      - true

source/command/atlas-api-alertConfigurations-deleteAlertConfiguration.txt

@@ -14,7 +14,14 @@ atlas api alertConfigurations deleteAlertConfiguration
 
 `experimental <https://www.mongodb.com/docs/atlas/cli/current/command/atlas-api/>`_: Removes one alert configuration from the specified project.
 
-To use this resource, the requesting API Key must have the Organization Owner or Project Owner role. This resource remains under revision and may change. This command is invoking the endpoint with OperationID: 'deleteAlertConfiguration'. For more information about flags, format of --file and examples, see: https://www.mongodb.com/docs/atlas/reference/api-resources-spec/v2/#tag/Alert-Configurations/operation/deleteAlertConfiguration
+To use this resource, the requesting API Key must have the Organization Owner or Project Owner role.
+
+
+This resource remains under revision and may change.
+
+This command is autogenerated and corresponds 1:1 with the Atlas API endpoint https://www.mongodb.com/docs/atlas/reference/api-resources-spec/v2/#tag/Alert-Configurations/operation/deleteAlertConfiguration.
+
+For more information and examples, see the referenced API documentation linked above.
 
 Syntax
 ------

source/command/atlas-api-alertConfigurations-getAlertConfiguration.txt

@@ -14,7 +14,14 @@ atlas api alertConfigurations getAlertConfiguration
 
 `experimental <https://www.mongodb.com/docs/atlas/cli/current/command/atlas-api/>`_: Returns the specified alert configuration from the specified project.
 
-To use this resource, the requesting API Key must have the Project Read Only role. This resource remains under revision and may change. This command is invoking the endpoint with OperationID: 'getAlertConfiguration'. For more information about flags, format of --file and examples, see: https://www.mongodb.com/docs/atlas/reference/api-resources-spec/v2/#tag/Alert-Configurations/operation/getAlertConfiguration
+To use this resource, the requesting API Key must have the Project Read Only role.
+
+
+This resource remains under revision and may change.
+
+This command is autogenerated and corresponds 1:1 with the Atlas API endpoint https://www.mongodb.com/docs/atlas/reference/api-resources-spec/v2/#tag/Alert-Configurations/operation/getAlertConfiguration.
+
+For more information and examples, see the referenced API documentation linked above.
 
 Syntax
 ------

source/command/atlas-api-alertConfigurations-listAlertConfigurationMatchersFieldNames.txt

@@ -14,7 +14,11 @@ atlas api alertConfigurations listAlertConfigurationMatchersFieldNames
 
 `experimental <https://www.mongodb.com/docs/atlas/cli/current/command/atlas-api/>`_: Get all field names that the matchers.fieldName parameter accepts when you create or update an Alert Configuration.
 
-You can successfully call this endpoint with any assigned role. This command is invoking the endpoint with OperationID: 'listAlertConfigurationMatchersFieldNames'. For more information about flags, format of --file and examples, see: https://www.mongodb.com/docs/atlas/reference/api-resources-spec/v2/#tag/Alert-Configurations/operation/listAlertConfigurationMatchersFieldNames
+You can successfully call this endpoint with any assigned role.
+
+This command is autogenerated and corresponds 1:1 with the Atlas API endpoint https://www.mongodb.com/docs/atlas/reference/api-resources-spec/v2/#tag/Alert-Configurations/operation/listAlertConfigurationMatchersFieldNames.
+
+For more information and examples, see the referenced API documentation linked above.
 
 Syntax
 ------

source/command/atlas-api-alertConfigurations-listAlertConfigurations.txt

@@ -14,7 +14,14 @@ atlas api alertConfigurations listAlertConfigurations
 
 `experimental <https://www.mongodb.com/docs/atlas/cli/current/command/atlas-api/>`_: Returns all alert configurations for one project.
 
-These alert configurations apply to any component in the project. Alert configurations define the triggers and notification methods for alerts. To use this resource, the requesting API Key must have the Project Read Only role. This resource remains under revision and may change. This command is invoking the endpoint with OperationID: 'listAlertConfigurations'. For more information about flags, format of --file and examples, see: https://www.mongodb.com/docs/atlas/reference/api-resources-spec/v2/#tag/Alert-Configurations/operation/listAlertConfigurations
+These alert configurations apply to any component in the project. Alert configurations define the triggers and notification methods for alerts. To use this resource, the requesting API Key must have the Project Read Only role.
+
+
+This resource remains under revision and may change.
+
+This command is autogenerated and corresponds 1:1 with the Atlas API endpoint https://www.mongodb.com/docs/atlas/reference/api-resources-spec/v2/#tag/Alert-Configurations/operation/listAlertConfigurations.
+
+For more information and examples, see the referenced API documentation linked above.
 
 Syntax
 ------

source/command/atlas-api-alertConfigurations-listAlertConfigurationsByAlertId.txt

@@ -14,7 +14,14 @@ atlas api alertConfigurations listAlertConfigurationsByAlertId
 
 `experimental <https://www.mongodb.com/docs/atlas/cli/current/command/atlas-api/>`_: Returns all alert configurations set for the specified alert.
 
-To use this resource, the requesting API Key must have the Project Read Only role. This resource remains under revision and may change. This command is invoking the endpoint with OperationID: 'listAlertConfigurationsByAlertId'. For more information about flags, format of --file and examples, see: https://www.mongodb.com/docs/atlas/reference/api-resources-spec/v2/#tag/Alert-Configurations/operation/listAlertConfigurationsByAlertId
+To use this resource, the requesting API Key must have the Project Read Only role.
+
+
+This resource remains under revision and may change.
+
+This command is autogenerated and corresponds 1:1 with the Atlas API endpoint https://www.mongodb.com/docs/atlas/reference/api-resources-spec/v2/#tag/Alert-Configurations/operation/listAlertConfigurationsByAlertId.
+
+For more information and examples, see the referenced API documentation linked above.
 
 Syntax
 ------