From fbb0bdeaae2e3e43b1faaa3c3336fe6bb2703ab9 Mon Sep 17 00:00:00 2001 From: "ci.datadog-api-spec" Date: Mon, 2 Nov 2026 20:11:42 +0000 Subject: [PATCH] Regenerate client from commit 5caddbc of spec repo --- .generator/schemas/v2/openapi.yaml | 32 +++++++++++++++++-- .../v2/api/usage_metering_api.py | 28 ++++++++++++++++ .../usage_quota_bulk_result_attributes.py | 2 +- .../v2/model/usage_quota_create_attributes.py | 2 +- .../v2/model/usage_quota_request_scope.py | 2 +- .../model/usage_quota_response_attributes.py | 2 +- .../v2/model/usage_quota_response_scope.py | 2 +- 7 files changed, 63 insertions(+), 7 deletions(-) diff --git a/.generator/schemas/v2/openapi.yaml b/.generator/schemas/v2/openapi.yaml index 24d89e059e..18de03711a 100644 --- a/.generator/schemas/v2/openapi.yaml +++ b/.generator/schemas/v2/openapi.yaml @@ -142769,7 +142769,7 @@ components: additionalProperties: example: jane@example.com type: string - description: A namespace-specific key and value identifying what the quota applies to within an organization. The object must contain exactly one entry. Use `"*"` as the value for the default quota applied to entities without a specific quota, or omit the scope for an organization-wide quota. A specific value must identify an existing user handle in the caller's organization when `include_descendants` is false. When `include_descendants` is true, the handle must exist in the caller's organization or in at least one targeted descendant organization; the quota is then applied only to the organizations where that handle exists, and the request fails only if the handle exists in none of them. + description: A namespace-specific key and value identifying what the quota applies to within an organization. See the endpoint description for the supported scope keys, values, and validation rules. example: user_handle: jane@example.com maxProperties: 1 @@ -142844,7 +142844,7 @@ components: additionalProperties: example: jane@example.com type: string - description: A namespace-specific key and value identifying what the quota applies to within an organization. The object contains exactly one entry. A value of `"*"` identifies the default quota applied to entities without a specific quota. This field is omitted for an organization-wide quota. + description: A namespace-specific key and value identifying what the quota applies to within an organization. The object contains exactly one entry. A `user_handle` value of `"*"` identifies the default quota applied to users without a specific quota. This field is omitted for an organization-wide quota. example: user_handle: jane@example.com maxProperties: 1 @@ -254501,6 +254501,34 @@ paths: For the organization-wide quota, `pending_usage_limit` schedules a limit for the next usage period and can accompany an immediate limit or update an existing quota by itself. Scheduled changes follow `include_descendants` like the other fields. Requires the `billing_edit` permission. + + ### Quota namespaces and scope keys + + The `quota_namespace` path parameter selects the product whose usage quotas are managed. Each namespace + supports its own scope keys, described below. Omit `scope` for the organization-wide quota. + + #### `ai_credits` scope keys + + Each item's `scope` contains exactly one of the following keys. + + **`user_handle`** + + - **Value:** The handle of a user, for example `jane@example.com`, or `"*"` for the default quota applied to + users without a specific quota. User handles are returned in the `data[].attributes.handle` field by the + [Users API](https://docs.datadoghq.com/api/latest/users/#list-all-users). + - **Validation:** A specific handle must identify an existing user in the caller's organization when + `include_descendants` is false. When `include_descendants` is true, the handle must exist in the caller's + organization or in at least one targeted descendant organization. The quota is then applied only to the + organizations where the handle exists, and the item fails only if the handle exists in none of them. + + **`role_uuid`** + + - **Value:** The UUID of a role, for example `12345678-1234-1234-1234-123456789012`. `"*"` is not accepted + because there is no default role quota. Role UUIDs are returned in the `data[].id` field by the + [Roles API](https://docs.datadoghq.com/api/latest/roles/#list-roles). + - **Validation:** The role must exist in the caller's organization. Role UUIDs are unique, so + `include_descendants` has no effect on a `role_uuid` scope: the role is validated against the caller's + organization only. operationId: CreateQuotas parameters: - description: The product-specific namespace whose usage quotas are being managed. diff --git a/src/datadog_api_client/v2/api/usage_metering_api.py b/src/datadog_api_client/v2/api/usage_metering_api.py index 5f29e6ce04..83f44ed2a5 100644 --- a/src/datadog_api_client/v2/api/usage_metering_api.py +++ b/src/datadog_api_client/v2/api/usage_metering_api.py @@ -889,6 +889,34 @@ def create_quotas( accompany an immediate limit or update an existing quota by itself. Scheduled changes follow ``include_descendants`` like the other fields. Requires the ``billing_edit`` permission. + **Quota namespaces and scope keys** + + The ``quota_namespace`` path parameter selects the product whose usage quotas are managed. Each namespace + supports its own scope keys, described below. Omit ``scope`` for the organization-wide quota. + + **ai_credits scope keys** + + Each item's ``scope`` contains exactly one of the following keys. + + **user_handle** + + * **Value:** The handle of a user, for example ``jane@example.com`` , or ``"*"`` for the default quota applied to + users without a specific quota. User handles are returned in the ``data[].attributes.handle`` field by the + `Users API `_. + * **Validation:** A specific handle must identify an existing user in the caller's organization when + ``include_descendants`` is false. When ``include_descendants`` is true, the handle must exist in the caller's + organization or in at least one targeted descendant organization. The quota is then applied only to the + organizations where the handle exists, and the item fails only if the handle exists in none of them. + + **role_uuid** + + * **Value:** The UUID of a role, for example ``12345678-1234-1234-1234-123456789012``. ``"*"`` is not accepted + because there is no default role quota. Role UUIDs are returned in the ``data[].id`` field by the + `Roles API `_. + * **Validation:** The role must exist in the caller's organization. Role UUIDs are unique, so + ``include_descendants`` has no effect on a ``role_uuid`` scope: the role is validated against the caller's + organization only. + :param quota_namespace: The product-specific namespace whose usage quotas are being managed. :type quota_namespace: str :param body: The usage quotas to create or update. diff --git a/src/datadog_api_client/v2/model/usage_quota_bulk_result_attributes.py b/src/datadog_api_client/v2/model/usage_quota_bulk_result_attributes.py index 8808447a22..9ef6abe1dd 100644 --- a/src/datadog_api_client/v2/model/usage_quota_bulk_result_attributes.py +++ b/src/datadog_api_client/v2/model/usage_quota_bulk_result_attributes.py @@ -75,7 +75,7 @@ def __init__( :param pending_usage_limit: The usage limit scheduled for the organization-wide quota in the usage units defined by the quota namespace. A value of ``0`` is valid. At the start of the effective month, this value becomes ``usage_limit`` and both pending fields are omitted. Omitted when no change is scheduled or this item failed to write. :type pending_usage_limit: float, optional - :param scope: A namespace-specific key and value identifying what the quota applies to within an organization. The object contains exactly one entry. A value of ``"*"`` identifies the default quota applied to entities without a specific quota. This field is omitted for an organization-wide quota. + :param scope: A namespace-specific key and value identifying what the quota applies to within an organization. The object contains exactly one entry. A ``user_handle`` value of ``"*"`` identifies the default quota applied to users without a specific quota. This field is omitted for an organization-wide quota. :type scope: UsageQuotaResponseScope, optional :param usage_limit: The quota limit in the usage units defined by the quota namespace. May be fractional for quotas configured before public writes required whole units. Omitted if this item failed to write. diff --git a/src/datadog_api_client/v2/model/usage_quota_create_attributes.py b/src/datadog_api_client/v2/model/usage_quota_create_attributes.py index 6c97763b3e..37cac7cb6f 100644 --- a/src/datadog_api_client/v2/model/usage_quota_create_attributes.py +++ b/src/datadog_api_client/v2/model/usage_quota_create_attributes.py @@ -62,7 +62,7 @@ def __init__( :param pending_usage_limit: The non-negative, whole-number limit to schedule for the organization-wide quota in the usage units defined by the quota namespace. It is not checked against current usage. Each write schedules the value for 00:00 UTC on the first day of the next calendar month and replaces any previously scheduled change; the server computes ``pending_effective_from``. Omit this field to leave any scheduled change unchanged, including when raising ``usage_limit``. Cancel a scheduled change only by deleting the quota's ``/pending`` sub-resource. :type pending_usage_limit: int, optional - :param scope: A namespace-specific key and value identifying what the quota applies to within an organization. The object must contain exactly one entry. Use ``"*"`` as the value for the default quota applied to entities without a specific quota, or omit the scope for an organization-wide quota. A specific value must identify an existing user handle in the caller's organization when ``include_descendants`` is false. When ``include_descendants`` is true, the handle must exist in the caller's organization or in at least one targeted descendant organization; the quota is then applied only to the organizations where that handle exists, and the request fails only if the handle exists in none of them. + :param scope: A namespace-specific key and value identifying what the quota applies to within an organization. See the endpoint description for the supported scope keys, values, and validation rules. :type scope: UsageQuotaRequestScope, optional :param usage_limit: The non-negative, whole-number quota limit to set in the usage units defined by the quota namespace. For an organization-wide quota (scope omitted), the limit must be greater than usage already recorded in the current period. When this field is provided, ``enforced`` is required. diff --git a/src/datadog_api_client/v2/model/usage_quota_request_scope.py b/src/datadog_api_client/v2/model/usage_quota_request_scope.py index b57894e7c9..8720041e83 100644 --- a/src/datadog_api_client/v2/model/usage_quota_request_scope.py +++ b/src/datadog_api_client/v2/model/usage_quota_request_scope.py @@ -17,6 +17,6 @@ def additional_properties_type(_): def __init__(self_, **kwargs): """ - A namespace-specific key and value identifying what the quota applies to within an organization. The object must contain exactly one entry. Use ``"*"`` as the value for the default quota applied to entities without a specific quota, or omit the scope for an organization-wide quota. A specific value must identify an existing user handle in the caller's organization when ``include_descendants`` is false. When ``include_descendants`` is true, the handle must exist in the caller's organization or in at least one targeted descendant organization; the quota is then applied only to the organizations where that handle exists, and the request fails only if the handle exists in none of them. + A namespace-specific key and value identifying what the quota applies to within an organization. See the endpoint description for the supported scope keys, values, and validation rules. """ super().__init__(kwargs) diff --git a/src/datadog_api_client/v2/model/usage_quota_response_attributes.py b/src/datadog_api_client/v2/model/usage_quota_response_attributes.py index bc266d222f..a8a1518033 100644 --- a/src/datadog_api_client/v2/model/usage_quota_response_attributes.py +++ b/src/datadog_api_client/v2/model/usage_quota_response_attributes.py @@ -71,7 +71,7 @@ def __init__( fields are omitted. Omitted when no change is scheduled. :type pending_usage_limit: float, optional - :param scope: A namespace-specific key and value identifying what the quota applies to within an organization. The object contains exactly one entry. A value of ``"*"`` identifies the default quota applied to entities without a specific quota. This field is omitted for an organization-wide quota. + :param scope: A namespace-specific key and value identifying what the quota applies to within an organization. The object contains exactly one entry. A ``user_handle`` value of ``"*"`` identifies the default quota applied to users without a specific quota. This field is omitted for an organization-wide quota. :type scope: UsageQuotaResponseScope, optional :param usage_limit: The quota limit in the usage units defined by the quota namespace. May be fractional for quotas configured before public writes required whole units. diff --git a/src/datadog_api_client/v2/model/usage_quota_response_scope.py b/src/datadog_api_client/v2/model/usage_quota_response_scope.py index d93b038bc0..c9353ed35d 100644 --- a/src/datadog_api_client/v2/model/usage_quota_response_scope.py +++ b/src/datadog_api_client/v2/model/usage_quota_response_scope.py @@ -17,6 +17,6 @@ def additional_properties_type(_): def __init__(self_, **kwargs): """ - A namespace-specific key and value identifying what the quota applies to within an organization. The object contains exactly one entry. A value of ``"*"`` identifies the default quota applied to entities without a specific quota. This field is omitted for an organization-wide quota. + A namespace-specific key and value identifying what the quota applies to within an organization. The object contains exactly one entry. A ``user_handle`` value of ``"*"`` identifies the default quota applied to users without a specific quota. This field is omitted for an organization-wide quota. """ super().__init__(kwargs)