[pull] master from DataDog:master

.generated-info

@@ -1,4 +1,4 @@
 {
-  "spec_repo_commit": "672a533",
-  "generated": "2025-07-31 18:07:39.883"
+  "spec_repo_commit": "35630f3",
+  "generated": "2025-08-01 18:17:22.417"
 }

.generator/schemas/v2/openapi.yaml

@@ -766,7 +766,8 @@ components:
       description: 'Identifier, formatted as `type:id`. Supported types: `dashboard`,
         `integration-service`, `integration-webhook`, `notebook`, `reference-table`,
         `security-rule`, `slo`, `workflow`, `app-builder-app`, `connection`, `connection-group`,
-        `rum-application`, `cross-org-connection`, `spreadsheet`.'
+        `rum-application`, `cross-org-connection`, `spreadsheet`, `on-call-schedule`,
+        `on-call-escalation-policy`, `on-call-team-routing-rules.'
       example: dashboard:abc-def-ghi
       in: path
       name: resource_id
@@ -59320,6 +59321,12 @@ paths:
 
         - Spreadsheets: `spreadsheet`
 
+        - On-Call Schedules: `on-call-schedule`
+
+        - On-Call Escalation Policies: `on-call-escalation-policy`
+
+        - On-Call Team Routing Rules: `on-call-team-routing-rules`
+
 
         #### Supported relations for resources
 
@@ -59363,7 +59370,13 @@ paths:
 
         Cross Org Connections       | `viewer`, `editor`
 
-        Spreadsheets                | `viewer`, `editor`'
+        Spreadsheets                | `viewer`, `editor`
+
+        On-Call Schedules           | `viewer`, `overrider`, `editor`
+
+        On-Call Escalation Policies | `viewer`, `editor`
+
+        On-Call Team Routing Rules  | `viewer`, `editor`'
       operationId: UpdateRestrictionPolicy
       parameters:
       - $ref: '#/components/parameters/ResourceID'

features/v2/datasets.feature

@@ -11,15 +11,15 @@ Feature: Datasets
     And a valid "appKeyAuth" key in the system
     And an instance of "Datasets" API
 
-  @skip-go @skip-java @skip-python @skip-ruby @skip-rust @skip-typescript @skip-validation @team:DataDog/aaa-granular-access
+  @skip-go @skip-java @skip-python @skip-ruby @skip-rust @skip-terraform-config @skip-typescript @skip-validation @team:DataDog/aaa-granular-access
   Scenario: Create a dataset returns "Bad Request" response
     Given new "CreateDataset" request
     And operation "CreateDataset" enabled
     And body with value {"test": "bad_request"}
     When the request is sent
     Then the response status is 400 Bad Request
 
-  @team:DataDog/aaa-granular-access
+  @skip-terraform-config @team:DataDog/aaa-granular-access
   Scenario: Create a dataset returns "Conflict" response
     Given there is a valid "dataset" in the system
     And operation "CreateDataset" enabled
@@ -28,23 +28,23 @@ Feature: Datasets
     When the request is sent
     Then the response status is 409 Conflict
 
-  @team:DataDog/aaa-granular-access
+  @skip-terraform-config @team:DataDog/aaa-granular-access
   Scenario: Create a dataset returns "OK" response
     Given new "CreateDataset" request
     And operation "CreateDataset" enabled
     And body with value {"data": {"attributes": {"name": "Security Audit Dataset", "principals": ["role:94172442-be03-11e9-a77a-3b7612558ac1"], "product_filters": [{"filters": ["@application.id:ABCD"], "product": "metrics"}]}, "type": "dataset"}}
     When the request is sent
     Then the response status is 200 OK
 
-  @team:DataDog/aaa-granular-access
+  @skip-terraform-config @team:DataDog/aaa-granular-access
   Scenario: Delete a dataset returns "Bad Request" response
     Given new "DeleteDataset" request
     And operation "DeleteDataset" enabled
     And request contains "dataset_id" parameter with value "malformed_id"
     When the request is sent
     Then the response status is 400 Bad Request
 
-  @team:DataDog/aaa-granular-access
+  @skip-terraform-config @team:DataDog/aaa-granular-access
   Scenario: Delete a dataset returns "No Content" response
     Given there is a valid "dataset" in the system
     And operation "DeleteDataset" enabled
@@ -53,23 +53,23 @@ Feature: Datasets
     When the request is sent
     Then the response status is 204 No Content
 
-  @team:DataDog/aaa-granular-access
+  @skip-terraform-config @team:DataDog/aaa-granular-access
   Scenario: Delete a dataset returns "Not Found" response
     Given new "DeleteDataset" request
     And operation "DeleteDataset" enabled
     And request contains "dataset_id" parameter with value "00000000-0000-0000-0000-000000000000"
     When the request is sent
     Then the response status is 404 Not Found
 
-  @skip-go @skip-java @skip-python @skip-ruby @skip-rust @skip-typescript @skip-validation @team:DataDog/aaa-granular-access
+  @skip-go @skip-java @skip-python @skip-ruby @skip-rust @skip-terraform-config @skip-typescript @skip-validation @team:DataDog/aaa-granular-access
   Scenario: Edit a dataset returns "Bad Request" response
     Given new "UpdateDataset" request
     And operation "UpdateDataset" enabled
     And request contains "dataset_id" parameter with value "malformed_id"
     When the request is sent
     Then the response status is 400 Bad Request
 
-  @skip @team:DataDog/aaa-granular-access
+  @skip @skip-terraform-config @team:DataDog/aaa-granular-access
   Scenario: Edit a dataset returns "Not Found" response
     Given there is a valid "dataset" in the system
     And operation "UpdateDataset" enabled
@@ -79,7 +79,7 @@ Feature: Datasets
     When the request is sent
     Then the response status is 404 Not Found
 
-  @team:DataDog/aaa-granular-access
+  @skip-terraform-config @team:DataDog/aaa-granular-access
   Scenario: Edit a dataset returns "OK" response
     Given there is a valid "dataset" in the system
     And operation "UpdateDataset" enabled
@@ -89,23 +89,23 @@ Feature: Datasets
     When the request is sent
     Then the response status is 200 OK
 
-  @team:DataDog/aaa-granular-access
+  @skip-terraform-config @team:DataDog/aaa-granular-access
   Scenario: Get a single dataset by ID returns "Bad Request" response
     Given new "GetDataset" request
     And operation "GetDataset" enabled
     And request contains "dataset_id" parameter with value "malformed_id"
     When the request is sent
     Then the response status is 400 Bad Request
 
-  @skip @team:DataDog/aaa-granular-access
+  @skip @skip-terraform-config @team:DataDog/aaa-granular-access
   Scenario: Get a single dataset by ID returns "Not Found" response
     Given operation "GetDataset" enabled
     And new "GetDataset" request
     And request contains "dataset_id" parameter with value "00000000-0000-0000-0000-000000000000"
     When the request is sent
     Then the response status is 404 Not Found
 
-  @team:DataDog/aaa-granular-access
+  @skip-terraform-config @team:DataDog/aaa-granular-access
   Scenario: Get a single dataset by ID returns "OK" response
     Given there is a valid "dataset" in the system
     And operation "GetDataset" enabled
@@ -114,7 +114,7 @@ Feature: Datasets
     When the request is sent
     Then the response status is 200 OK
 
-  @team:DataDog/aaa-granular-access
+  @skip-terraform-config @team:DataDog/aaa-granular-access
   Scenario: Get all datasets returns "OK" response
     Given there is a valid "dataset" in the system
     And operation "GetAllDatasets" enabled

lib/datadog_api_client/v2/api/restriction_policies_api.rb

@@ -35,7 +35,7 @@ def delete_restriction_policy(resource_id, opts = {})
     #
     # Deletes the restriction policy associated with a specified resource.
     #
-    # @param resource_id [String] Identifier, formatted as `type:id`. Supported types: `dashboard`, `integration-service`, `integration-webhook`, `notebook`, `reference-table`, `security-rule`, `slo`, `workflow`, `app-builder-app`, `connection`, `connection-group`, `rum-application`, `cross-org-connection`, `spreadsheet`.
+    # @param resource_id [String] Identifier, formatted as `type:id`. Supported types: `dashboard`, `integration-service`, `integration-webhook`, `notebook`, `reference-table`, `security-rule`, `slo`, `workflow`, `app-builder-app`, `connection`, `connection-group`, `rum-application`, `cross-org-connection`, `spreadsheet`, `on-call-schedule`, `on-call-escalation-policy`, `on-call-team-routing-rules.
     # @param opts [Hash] the optional parameters
     # @return [Array<(nil, Integer, Hash)>] nil, response status code and response headers
     def delete_restriction_policy_with_http_info(resource_id, opts = {})
@@ -100,7 +100,7 @@ def get_restriction_policy(resource_id, opts = {})
     #
     # Retrieves the restriction policy associated with a specified resource.
     #
-    # @param resource_id [String] Identifier, formatted as `type:id`. Supported types: `dashboard`, `integration-service`, `integration-webhook`, `notebook`, `reference-table`, `security-rule`, `slo`, `workflow`, `app-builder-app`, `connection`, `connection-group`, `rum-application`, `cross-org-connection`, `spreadsheet`.
+    # @param resource_id [String] Identifier, formatted as `type:id`. Supported types: `dashboard`, `integration-service`, `integration-webhook`, `notebook`, `reference-table`, `security-rule`, `slo`, `workflow`, `app-builder-app`, `connection`, `connection-group`, `rum-application`, `cross-org-connection`, `spreadsheet`, `on-call-schedule`, `on-call-escalation-policy`, `on-call-team-routing-rules.
     # @param opts [Hash] the optional parameters
     # @return [Array<(RestrictionPolicyResponse, Integer, Hash)>] RestrictionPolicyResponse data, response status code and response headers
     def get_restriction_policy_with_http_info(resource_id, opts = {})
@@ -186,6 +186,9 @@ def update_restriction_policy(resource_id, body, opts = {})
     # - RUM Applications: `rum-application`
     # - Cross Org Connections: `cross-org-connection`
     # - Spreadsheets: `spreadsheet`
+    # - On-Call Schedules: `on-call-schedule`
+    # - On-Call Escalation Policies: `on-call-escalation-policy`
+    # - On-Call Team Routing Rules: `on-call-team-routing-rules`
     #
     # #### Supported relations for resources
     # Resource Type               | Supported Relations
@@ -209,8 +212,11 @@ def update_restriction_policy(resource_id, body, opts = {})
     # RUM Application             | `viewer`, `editor`
     # Cross Org Connections       | `viewer`, `editor`
     # Spreadsheets                | `viewer`, `editor`
+    # On-Call Schedules           | `viewer`, `overrider`, `editor`
+    # On-Call Escalation Policies | `viewer`, `editor`
+    # On-Call Team Routing Rules  | `viewer`, `editor`
     #
-    # @param resource_id [String] Identifier, formatted as `type:id`. Supported types: `dashboard`, `integration-service`, `integration-webhook`, `notebook`, `reference-table`, `security-rule`, `slo`, `workflow`, `app-builder-app`, `connection`, `connection-group`, `rum-application`, `cross-org-connection`, `spreadsheet`.
+    # @param resource_id [String] Identifier, formatted as `type:id`. Supported types: `dashboard`, `integration-service`, `integration-webhook`, `notebook`, `reference-table`, `security-rule`, `slo`, `workflow`, `app-builder-app`, `connection`, `connection-group`, `rum-application`, `cross-org-connection`, `spreadsheet`, `on-call-schedule`, `on-call-escalation-policy`, `on-call-team-routing-rules.
     # @param body [RestrictionPolicyUpdateRequest] Restriction policy payload
     # @param opts [Hash] the optional parameters
     # @option opts [Boolean] :allow_self_lockout Allows admins (users with the `user_access_manage` permission) to remove their own access from the resource if set to `true`. By default, this is set to `false`, preventing admins from locking themselves out.