Regenerate client from commit bdb7b215 of spec repo

Author: ci.datadog-api-spec

.apigentools-info

@@ -4,13 +4,13 @@
     "spec_versions": {
         "v1": {
             "apigentools_version": "1.6.6",
-            "regenerated": "2024-01-24 20:59:46.831321",
-            "spec_repo_commit": "9d7a3d85"
+            "regenerated": "2024-01-25 15:52:47.844285",
+            "spec_repo_commit": "bdb7b215"
         },
         "v2": {
             "apigentools_version": "1.6.6",
-            "regenerated": "2024-01-24 20:59:46.846226",
-            "spec_repo_commit": "9d7a3d85"
+            "regenerated": "2024-01-25 15:52:47.860458",
+            "spec_repo_commit": "bdb7b215"
         }
     }
 }

.generator/schemas/v2/openapi.yaml

@@ -16759,8 +16759,11 @@ components:
         expiration_date:
           description: A Unix millisecond timestamp giving an expiration date for
             the suppression rule. After this date, it won't suppress signals anymore.
+            If unset, the expiration date of the suppression rule is left untouched.
+            If set to `null`, the expiration date is removed.
           example: 1703187336000
           format: int64
+          nullable: true
           type: integer
         name:
           description: The name of the suppression rule.

packages/datadog-api-client-v2/models/SecurityMonitoringSuppressionUpdateAttributes.ts

@@ -19,7 +19,7 @@ export class SecurityMonitoringSuppressionUpdateAttributes {
    */
   "enabled"?: boolean;
   /**
-   * A Unix millisecond timestamp giving an expiration date for the suppression rule. After this date, it won't suppress signals anymore.
+   * A Unix millisecond timestamp giving an expiration date for the suppression rule. After this date, it won't suppress signals anymore. If unset, the expiration date of the suppression rule is left untouched. If set to `null`, the expiration date is removed.
    */
   "expirationDate"?: number;
   /**