From f438b40d6e5d20ef2eb51cbbe46d0600358785a0 Mon Sep 17 00:00:00 2001
From: "ci.datadog-api-spec" <packages@datadoghq.com>
Date: Thu, 20 Aug 2026 17:26:52 +0000
Subject: [PATCH] Regenerate client from commit 4697b4f of spec repo

---
 .generator/schemas/v2/openapi.yaml                 | 14 ++++++++++++--
 .../datadog/api/client/v2/api/FeatureFlagsApi.java |  9 +++++++--
 .../client/v2/model/UpsertAllocationRequest.java   |  4 +++-
 3 files changed, 22 insertions(+), 5 deletions(-)

diff --git a/.generator/schemas/v2/openapi.yaml b/.generator/schemas/v2/openapi.yaml
index cd024ee1689..ab889acf9f7 100644
--- a/.generator/schemas/v2/openapi.yaml
+++ b/.generator/schemas/v2/openapi.yaml
@@ -117110,7 +117110,10 @@ components:
       description: Request to create or update a targeting rule (allocation) for a feature flag environment.
       properties:
         experiment_id:
-          description: The experiment ID for experiment-linked allocations.
+          description: |-
+            The experiment ID linked to the allocation. For `FEATURE_GATE` allocations,
+            a non-null value denotes a standard experiment. For `CANARY` allocations,
+            Datadog manages this value. Omit it when creating a canary allocation.
           example: "550e8400-e29b-41d4-a716-446655440030"
           nullable: true
           type: string
@@ -144699,6 +144702,11 @@ paths:
       description: |-
         Updates targeting rules (allocations) for a specific feature flag in a specific environment.
         This operation replaces the existing allocation set with the request payload.
+        Creating, updating, or deleting a standard experiment allocation—an allocation with
+        `type: FEATURE_GATE` and a non-null `experiment_id`—also requires the
+        `product_analytics_experiments_write` permission. This additional permission is not
+        required for `CANARY` allocations, exposure schedules, or guardrail metrics unless
+        the same operation also mutates a standard experiment allocation.
       operationId: UpdateAllocationsForFeatureFlagInEnvironment
       parameters:
         - $ref: "#/components/parameters/feature_flag_id"
@@ -144772,7 +144780,9 @@ paths:
             application/json:
               schema:
                 $ref: "#/components/schemas/APIErrorResponse"
-          description: Forbidden
+          description: |-
+            Forbidden. The caller is missing the `feature_flag_config_write` permission.
+            This error is also returned when the operation mutates a standard experiment allocation and the caller is missing the `product_analytics_experiments_write` permission.
         "404":
           content:
             application/json:
diff --git a/src/main/java/com/datadog/api/client/v2/api/FeatureFlagsApi.java b/src/main/java/com/datadog/api/client/v2/api/FeatureFlagsApi.java
index ad5430c1538..f842802ffbf 100644
--- a/src/main/java/com/datadog/api/client/v2/api/FeatureFlagsApi.java
+++ b/src/main/java/com/datadog/api/client/v2/api/FeatureFlagsApi.java
@@ -3006,7 +3006,12 @@ public ListAllocationsResponse updateAllocationsForFeatureFlagInEnvironment(
 
   /**
    * Updates targeting rules (allocations) for a specific feature flag in a specific environment.
-   * This operation replaces the existing allocation set with the request payload.
+   * This operation replaces the existing allocation set with the request payload. Creating,
+   * updating, or deleting a standard experiment allocation—an allocation with <code>
+   * type: FEATURE_GATE</code> and a non-null <code>experiment_id</code>—also requires the <code>
+   * product_analytics_experiments_write</code> permission. This additional permission is not
+   * required for <code>CANARY</code> allocations, exposure schedules, or guardrail metrics unless
+   * the same operation also mutates a standard experiment allocation.
    *
    * @param featureFlagId The ID of the feature flag. (required)
    * @param environmentId The ID of the environment. (required)
@@ -3020,7 +3025,7 @@ public ListAllocationsResponse updateAllocationsForFeatureFlagInEnvironment(
    *       <tr><td> 200 </td><td> OK </td><td>  -  </td></tr>
    *       <tr><td> 202 </td><td> Accepted - Approval required for this change </td><td>  -  </td></tr>
    *       <tr><td> 400 </td><td> Bad Request </td><td>  -  </td></tr>
-   *       <tr><td> 403 </td><td> Forbidden </td><td>  -  </td></tr>
+   *       <tr><td> 403 </td><td> Forbidden. The caller is missing the &#x60;feature_flag_config_write&#x60; permission. This error is also returned when the operation mutates a standard experiment allocation and the caller is missing the &#x60;product_analytics_experiments_write&#x60; permission. </td><td>  -  </td></tr>
    *       <tr><td> 404 </td><td> Not Found </td><td>  -  </td></tr>
    *       <tr><td> 409 </td><td> Conflict </td><td>  -  </td></tr>
    *       <tr><td> 429 </td><td> Too many requests </td><td>  -  </td></tr>
diff --git a/src/main/java/com/datadog/api/client/v2/model/UpsertAllocationRequest.java b/src/main/java/com/datadog/api/client/v2/model/UpsertAllocationRequest.java
index b4c66d67328..cab1e4a38d2 100644
--- a/src/main/java/com/datadog/api/client/v2/model/UpsertAllocationRequest.java
+++ b/src/main/java/com/datadog/api/client/v2/model/UpsertAllocationRequest.java
@@ -83,7 +83,9 @@ public UpsertAllocationRequest experimentId(String experimentId) {
   }
 
   /**
-   * The experiment ID for experiment-linked allocations.
+   * The experiment ID linked to the allocation. For <code>FEATURE_GATE</code> allocations, a
+   * non-null value denotes a standard experiment. For <code>CANARY</code> allocations, Datadog
+   * manages this value. Omit it when creating a canary allocation.
    *
    * @return experimentId
    */