From bfbb7b1e1b6bf52e3fb737f5f5d72298686cf571 Mon Sep 17 00:00:00 2001 From: "ci.datadog-api-spec" Date: Thu, 20 Aug 2026 17:36:01 +0000 Subject: [PATCH] Regenerate client from commit 4697b4f of spec repo --- .generator/schemas/v2/openapi.yaml | 14 ++++++++++++-- src/datadogV2/api/api_feature_flags.rs | 10 ++++++++++ .../model/model_upsert_allocation_request.rs | 4 +++- 3 files changed, 25 insertions(+), 3 deletions(-) diff --git a/.generator/schemas/v2/openapi.yaml b/.generator/schemas/v2/openapi.yaml index cd024ee168..ab889acf9f 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/datadogV2/api/api_feature_flags.rs b/src/datadogV2/api/api_feature_flags.rs index 9e8a43bb00..9e3b2d0cd9 100644 --- a/src/datadogV2/api/api_feature_flags.rs +++ b/src/datadogV2/api/api_feature_flags.rs @@ -2539,6 +2539,11 @@ impl FeatureFlagsAPI { /// 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. pub async fn update_allocations_for_feature_flag_in_environment( &self, feature_flag_id: uuid::Uuid, @@ -2571,6 +2576,11 @@ impl FeatureFlagsAPI { /// 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. pub async fn update_allocations_for_feature_flag_in_environment_with_http_info( &self, feature_flag_id: uuid::Uuid, diff --git a/src/datadogV2/model/model_upsert_allocation_request.rs b/src/datadogV2/model/model_upsert_allocation_request.rs index a10cf2072b..254e43919b 100644 --- a/src/datadogV2/model/model_upsert_allocation_request.rs +++ b/src/datadogV2/model/model_upsert_allocation_request.rs @@ -11,7 +11,9 @@ use std::fmt::{self, Formatter}; #[skip_serializing_none] #[derive(Clone, Debug, PartialEq, Serialize)] pub struct UpsertAllocationRequest { - /// The experiment ID for experiment-linked allocations. + /// 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. #[serde( rename = "experiment_id", default,