APIBot: SDK update based on recent changes in Atlas API (#430)

Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Co-authored-by: wtrocki <[email protected]>

Author: 3 people

admin/model_cluster_description20240805.go

@@ -60,7 +60,7 @@ type ClusterDescription20240805 struct {
 	Paused *bool `json:"paused,omitempty"`
 	// Flag that indicates whether the cluster uses continuous cloud backups.
 	PitEnabled *bool `json:"pitEnabled,omitempty"`
-	// Enable or disable log redaction.
+	// Enable or disable log redaction.  This setting configures the ``mongod`` or ``mongos`` to redact any document field contents from a message accompanying a given log event before logging. This prevents the program from writing potentially sensitive data stored on the database to the diagnostic log. Metadata such as error or operation codes, line numbers, and source file names are still visible in the logs.  Use ``redactClientLogData`` in conjunction with Encryption at Rest and TLS/SSL (Transport Encryption) to assist compliance with regulatory requirements.  *Note*: changing this setting on a cluster will trigger a rolling restart as soon as the cluster is updated.
 	RedactClientLogData *bool `json:"redactClientLogData,omitempty"`
 	// Set this field to configure the replica set scaling mode for your cluster.  By default, Atlas scales under WORKLOAD_TYPE. This mode allows Atlas to scale your analytics nodes in parallel to your operational nodes.  When configured as SEQUENTIAL, Atlas scales all nodes sequentially. This mode is intended for steady-state workloads and applications performing latency-sensitive secondary reads.  When configured as NODE_TYPE, Atlas scales your electable nodes in parallel with your read-only and analytics nodes. This mode is intended for large, dynamic workloads requiring frequent and timely cluster tier scaling. This is the fastest scaling strategy, but it might impact latency of workloads when performing extensive secondary reads.
 	ReplicaSetScalingStrategy *string `json:"replicaSetScalingStrategy,omitempty"`

docs/docs/ClusterDescription20240805.md

@@ -27,7 +27,7 @@ Name | Type | Description | Notes
 **Name** | Pointer to **string** | Human-readable label that identifies the cluster. | [optional] 
 **Paused** | Pointer to **bool** | Flag that indicates whether the cluster is paused. | [optional] 
 **PitEnabled** | Pointer to **bool** | Flag that indicates whether the cluster uses continuous cloud backups. | [optional] 
-**RedactClientLogData** | Pointer to **bool** | Enable or disable log redaction. | [optional] 
+**RedactClientLogData** | Pointer to **bool** | Enable or disable log redaction.  This setting configures the ``mongod`` or ``mongos`` to redact any document field contents from a message accompanying a given log event before logging. This prevents the program from writing potentially sensitive data stored on the database to the diagnostic log. Metadata such as error or operation codes, line numbers, and source file names are still visible in the logs.  Use ``redactClientLogData`` in conjunction with Encryption at Rest and TLS/SSL (Transport Encryption) to assist compliance with regulatory requirements.  *Note*: changing this setting on a cluster will trigger a rolling restart as soon as the cluster is updated. | [optional] 
 **ReplicaSetScalingStrategy** | Pointer to **string** | Set this field to configure the replica set scaling mode for your cluster.  By default, Atlas scales under WORKLOAD_TYPE. This mode allows Atlas to scale your analytics nodes in parallel to your operational nodes.  When configured as SEQUENTIAL, Atlas scales all nodes sequentially. This mode is intended for steady-state workloads and applications performing latency-sensitive secondary reads.  When configured as NODE_TYPE, Atlas scales your electable nodes in parallel with your read-only and analytics nodes. This mode is intended for large, dynamic workloads requiring frequent and timely cluster tier scaling. This is the fastest scaling strategy, but it might impact latency of workloads when performing extensive secondary reads. | [optional] [default to "WORKLOAD_TYPE"]
 **ReplicationSpecs** | Pointer to [**[]ReplicationSpec20240805**](ReplicationSpec20240805.md) | List of settings that configure your cluster regions. This array has one object per shard representing node configurations in each shard. For replica sets there is only one object representing node configurations. | [optional] 
 **RootCertType** | Pointer to **string** | Root Certificate Authority that MongoDB Cloud cluster uses. MongoDB Cloud supports Internet Security Research Group. | [optional] [default to "ISRGROOTX1"]

internal/core/version.go

@@ -5,7 +5,7 @@ package core
 // For more information please see: https://github.com/mongodb/atlas-sdk-go/blob/main/docs/doc_1_concepts.md
 const (
 	// SDK release tag version.
-	Version = "v20240805004.6.0"
+	Version = "v20240805004.7.0"
 	// Resource Version.
 	Resource = "20240805"
 )

openapi/atlas-api-transformed.yaml

@@ -27,7 +27,7 @@ info:
   termsOfService: https://www.mongodb.com/mongodb-management-service-terms-and-conditions
   title: MongoDB Atlas Administration API
   version: "2.0"
-  x-xgen-sha: 555299096548fddba749a9a882898b89a3580643
+  x-xgen-sha: ecc67f65d9b5a5199175facaab8a2dc97afe2911
 servers:
   - url: https://cloud.mongodb.com
 tags:
@@ -22375,18 +22375,20 @@ components:
             url: https://docs.atlas.mongodb.com/backup/cloud-backup/overview/
         redactClientLogData:
           type: boolean
-          description: Enable or disable log redaction.
-          externalDocs:
-            description: >-
-              This options corresponds to the ``security.redactClientLogData``
-              cluster parameter.
+          description: >-
+            Enable or disable log redaction.
 
 
-              This setting configures the ``mongod`` or ``mongos`` to redact any message accompanying a given log event before logging. This prevents the program from writing potentially sensitive data stored on the database to the diagnostic log. Metadata such as error or operation codes, line numbers, and source file names are still visible in the logs.
+            This setting configures the ``mongod`` or ``mongos`` to redact any document field contents from a message accompanying a given log event before logging. This prevents the program from writing potentially sensitive data stored on the database to the diagnostic log. Metadata such as error or operation codes, line numbers, and source file names are still visible in the logs.
 
 
-              Use ``redactClientLogData`` in conjunction with Encryption at Rest and TLS/SSL (Transport Encryption) to assist compliance with regulatory requirements.
-            url: https://www.mongodb.com/docs/manual/reference/parameters/#mongodb-parameter-param.redactClientLogData
+            Use ``redactClientLogData`` in conjunction with Encryption at Rest and TLS/SSL (Transport Encryption) to assist compliance with regulatory requirements.
+
+
+            *Note*: changing this setting on a cluster will trigger a rolling restart as soon as the cluster is updated.
+          externalDocs:
+            description: Log Redaction
+            url: https://www.mongodb.com/docs/manual/administration/monitoring/#log-redaction
         replicaSetScalingStrategy:
           type: string
           default: WORKLOAD_TYPE

openapi/atlas-api.yaml

@@ -21,7 +21,7 @@ info:
   termsOfService: https://www.mongodb.com/mongodb-management-service-terms-and-conditions
   title: MongoDB Atlas Administration API
   version: "2.0"
-  x-xgen-sha: 555299096548fddba749a9a882898b89a3580643
+  x-xgen-sha: ecc67f65d9b5a5199175facaab8a2dc97afe2911
 servers:
 - url: https://cloud.mongodb.com
 tags:
@@ -27887,15 +27887,17 @@ components:
             url: https://docs.atlas.mongodb.com/backup/cloud-backup/overview/
         redactClientLogData:
           type: boolean
-          description: Enable or disable log redaction.
-          externalDocs:
-            description: |-
-              This options corresponds to the ``security.redactClientLogData`` cluster parameter.
+          description: |-
+            Enable or disable log redaction.
 
-              This setting configures the ``mongod`` or ``mongos`` to redact any message accompanying a given log event before logging. This prevents the program from writing potentially sensitive data stored on the database to the diagnostic log. Metadata such as error or operation codes, line numbers, and source file names are still visible in the logs.
+            This setting configures the ``mongod`` or ``mongos`` to redact any document field contents from a message accompanying a given log event before logging. This prevents the program from writing potentially sensitive data stored on the database to the diagnostic log. Metadata such as error or operation codes, line numbers, and source file names are still visible in the logs.
 
-              Use ``redactClientLogData`` in conjunction with Encryption at Rest and TLS/SSL (Transport Encryption) to assist compliance with regulatory requirements.
-            url: https://www.mongodb.com/docs/manual/reference/parameters/#mongodb-parameter-param.redactClientLogData
+            Use ``redactClientLogData`` in conjunction with Encryption at Rest and TLS/SSL (Transport Encryption) to assist compliance with regulatory requirements.
+
+            *Note*: changing this setting on a cluster will trigger a rolling restart as soon as the cluster is updated.
+          externalDocs:
+            description: Log Redaction
+            url: https://www.mongodb.com/docs/manual/administration/monitoring/#log-redaction
         replicaSetScalingStrategy:
           type: string
           default: WORKLOAD_TYPE