You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .generator/schemas/v2/openapi.yaml
+258Lines changed: 258 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -21475,6 +21475,142 @@ components:
21475
21475
data:
21476
21476
$ref: "#/components/schemas/DatasetResponse"
21477
21477
type: object
21478
+
DatasetRestrictionOwnershipMode:
21479
+
description: Controls how dataset ownership is determined. `disabled` turns off ownership-based access entirely. `team_tag_based` assigns dataset ownership based on the team tags applied to the data, allowing team members to see their own team's datasets.
21480
+
enum:
21481
+
- disabled
21482
+
- team_tag_based
21483
+
example: "team_tag_based"
21484
+
type: string
21485
+
x-enum-varnames:
21486
+
- DISABLED
21487
+
- TEAM_TAG_BASED
21488
+
DatasetRestrictionPrincipal:
21489
+
description: A user or role that is exempt from dataset restrictions and retains unrestricted access to all datasets for the product type.
21490
+
properties:
21491
+
id:
21492
+
description: The unique identifier of the principal (a user UUID or role ID).
21493
+
example: "abc123"
21494
+
type: string
21495
+
name:
21496
+
description: The human-readable display name of the principal as shown in the Datadog UI.
21497
+
example: "Datadog Admin Role"
21498
+
type: string
21499
+
type:
21500
+
description: The kind of principal, such as `user` for an individual user account or `role` for a Datadog role.
21501
+
example: "role"
21502
+
type: string
21503
+
required:
21504
+
- type
21505
+
- id
21506
+
- name
21507
+
type: object
21508
+
DatasetRestrictionResponse:
21509
+
description: Response containing the updated dataset restriction.
description: Controls the default data visibility for the product type. `standard` makes data visible to all users with appropriate product access. `default_hide` hides data by default and requires explicit grants for each dataset.
21552
+
enum:
21553
+
- standard
21554
+
- default_hide
21555
+
example: "default_hide"
21556
+
type: string
21557
+
x-enum-varnames:
21558
+
- STANDARD
21559
+
- DEFAULT_HIDE
21560
+
DatasetRestrictionUpdateRequest:
21561
+
description: Payload for updating a dataset restriction configuration.
**Note**: This endpoint is in preview and is subject to change.
97551
+
If you have any feedback, contact [Datadog support](https://docs.datadoghq.com/help/).
97296
97552
/api/v2/datasets:
97297
97553
get:
97298
97554
description: Get all datasets that have been configured for an organization.
@@ -145632,6 +145888,8 @@ tags:
145632
145888
- description: |-
145633
145889
The Data Deletion API allows the user to target and delete data from the allowed products. It's currently enabled for Logs and RUM and depends on `logs_delete_data` and `rum_delete_data` permissions respectively.
145634
145890
name: Data Deletion
145891
+
- description: Configure dataset-level access restrictions per Datadog product type. Dataset restrictions control whether data is visible by default or hidden until explicitly granted, and how ownership-based access is determined.
145892
+
name: Dataset Restrictions
145635
145893
- description: |-
145636
145894
Data Access Controls in Datadog is a feature that allows administrators and access managers to regulate
145637
145895
access to sensitive data. By defining Restricted Datasets, you can ensure that only specific teams or roles can
Scenario: Update a dataset restriction returns "Bad Request" response
28
+
Given operation "UpdateDatasetRestriction" enabled
29
+
And new "UpdateDatasetRestriction" request
30
+
And request contains "product_type" parameter from "REPLACE.ME"
31
+
And body with value {"data": {"attributes": {"ownership_mode": "team_tag_based", "restriction_mode": "default_hide", "unrestricted_principals": []}, "type": "dataset_restrictions"}}
Scenario: Update a dataset restriction returns "Not Found" response
37
+
Given operation "UpdateDatasetRestriction" enabled
38
+
And new "UpdateDatasetRestriction" request
39
+
And request contains "product_type" parameter from "REPLACE.ME"
40
+
And body with value {"data": {"attributes": {"ownership_mode": "team_tag_based", "restriction_mode": "default_hide", "unrestricted_principals": []}, "type": "dataset_restrictions"}}
Scenario: Update a dataset restriction returns "OK" response
46
+
Given operation "UpdateDatasetRestriction" enabled
47
+
And new "UpdateDatasetRestriction" request
48
+
And request contains "product_type" parameter from "REPLACE.ME"
49
+
And body with value {"data": {"attributes": {"ownership_mode": "team_tag_based", "restriction_mode": "default_hide", "unrestricted_principals": []}, "type": "dataset_restrictions"}}
0 commit comments