Update rotation interval (#2516)

Co-authored-by: ci.datadog-api-spec <packages@datadoghq.com>

Author: api-clients-generation-pipeline[bot]

.apigentools-info

@@ -4,13 +4,13 @@
     "spec_versions": {
         "v1": {
             "apigentools_version": "1.6.6",
-            "regenerated": "2025-07-07 12:19:27.135140",
-            "spec_repo_commit": "fa2473ca"
+            "regenerated": "2025-07-08 07:29:02.458919",
+            "spec_repo_commit": "d9879085"
         },
         "v2": {
             "apigentools_version": "1.6.6",
-            "regenerated": "2025-07-07 12:19:27.153492",
-            "spec_repo_commit": "fa2473ca"
+            "regenerated": "2025-07-08 07:29:02.475424",
+            "spec_repo_commit": "d9879085"
         }
     }
 }

.generator/schemas/v2/openapi.yaml

@@ -758,7 +758,7 @@ components:
       description: 'Identifier, formatted as `type:id`. Supported types: `connection`,
         `dashboard`, `integration-account`, `integration-service`, `integration-webhook`,
         `notebook`, `reference-table`, `security-rule`, `slo`, `workflow`, `app-builder-app`,
-        `connection`, `connection-group`, `rum-application`.'
+        `connection`, `connection-group`, `rum-application`, `cross-org-connection`.'
       example: dashboard:abc-def-ghi
       in: path
       name: resource_id
@@ -20008,7 +20008,7 @@ components:
       type: object
     LayerAttributesInterval:
       description: Defines how often the rotation repeats, using a combination of
-        days and optional seconds.
+        days and optional seconds. Should be at least 1 hour.
       properties:
         days:
           description: The number of days in each rotation cycle.
@@ -33143,7 +33143,7 @@ components:
             - effective_date: '2025-02-03T05:00:00Z'
               end_date: '2025-12-31T00:00:00Z'
               interval:
-                seconds: 300
+                seconds: 3600
               members:
               - user:
                   id: 00000000-aba1-0000-0000-000000000000
@@ -56502,6 +56502,8 @@ paths:
 
         - RUM Applications: `rum-application`
 
+        - Cross Org Connections: `cross-org-connection`
+
 
         #### Supported relations for resources
 
@@ -56543,7 +56545,9 @@ paths:
 
         Connection Groups           | `viewer`, `editor`
 
-        RUM Application             | `viewer`, `editor`'
+        RUM Application             | `viewer`, `editor`
+
+        Cross Org Connections       | `viewer`, `editor`'
       operationId: UpdateRestrictionPolicy
       parameters:
       - $ref: '#/components/parameters/ResourceID'

cassettes/features/v2/on-call/Update-On-Call-schedule-returns-OK-response.frozen

@@ -1 +1 @@
-2025-05-29T04:54:24.605Z
+2025-07-03T14:30:45.232Z

cassettes/features/v2/on-call/Update-On-Call-schedule-returns-OK-response.yml

@@ -23,7 +23,7 @@
           effective_date: (Time.now + -10 * 86400),
           end_date: (Time.now + 10 * 86400),
           interval: DatadogAPIClient::V2::LayerAttributesInterval.new({
-            seconds: 300,
+            seconds: 3600,
           }),
           members: [
             DatadogAPIClient::V2::ScheduleRequestDataAttributesLayersItemsMembersItems.new({

examples/v2/on-call/UpdateOnCallSchedule.rb

@@ -221,15 +221,15 @@ Feature: On-Call
   Scenario: Update On-Call schedule returns "Bad Request" response
     Given new "UpdateOnCallSchedule" request
     And request contains "schedule_id" parameter from "REPLACE.ME"
-    And body with value {"data": {"attributes": {"layers": [{"effective_date": "2025-02-03T05:00:00Z", "end_date": "2025-12-31T00:00:00Z", "interval": {"seconds": 300}, "members": [{"user": {"id": "00000000-aba1-0000-0000-000000000000"}}], "name": "Layer 1", "restrictions": [{"end_day": "friday", "end_time": "17:00:00", "start_day": "monday", "start_time": "09:00:00"}], "rotation_start": "2025-02-01T00:00:00Z"}], "name": "On-Call Schedule Updated", "time_zone": "America/New_York"}, "id": "3653d3c6-0c75-11ea-ad28-fb5701eabc7d", "relationships": {"teams": {"data": [{"id": "00000000-da3a-0000-0000-000000000000", "type": "teams"}]}}, "type": "schedules"}}
+    And body with value {"data": {"attributes": {"layers": [{"effective_date": "2025-02-03T05:00:00Z", "end_date": "2025-12-31T00:00:00Z", "interval": {"seconds": 3600}, "members": [{"user": {"id": "00000000-aba1-0000-0000-000000000000"}}], "name": "Layer 1", "restrictions": [{"end_day": "friday", "end_time": "17:00:00", "start_day": "monday", "start_time": "09:00:00"}], "rotation_start": "2025-02-01T00:00:00Z"}], "name": "On-Call Schedule Updated", "time_zone": "America/New_York"}, "id": "3653d3c6-0c75-11ea-ad28-fb5701eabc7d", "relationships": {"teams": {"data": [{"id": "00000000-da3a-0000-0000-000000000000", "type": "teams"}]}}, "type": "schedules"}}
     When the request is sent
     Then the response status is 400 Bad Request
 
   @generated @skip @team:DataDog/bugle
   Scenario: Update On-Call schedule returns "Not Found" response
     Given new "UpdateOnCallSchedule" request
     And request contains "schedule_id" parameter from "REPLACE.ME"
-    And body with value {"data": {"attributes": {"layers": [{"effective_date": "2025-02-03T05:00:00Z", "end_date": "2025-12-31T00:00:00Z", "interval": {"seconds": 300}, "members": [{"user": {"id": "00000000-aba1-0000-0000-000000000000"}}], "name": "Layer 1", "restrictions": [{"end_day": "friday", "end_time": "17:00:00", "start_day": "monday", "start_time": "09:00:00"}], "rotation_start": "2025-02-01T00:00:00Z"}], "name": "On-Call Schedule Updated", "time_zone": "America/New_York"}, "id": "3653d3c6-0c75-11ea-ad28-fb5701eabc7d", "relationships": {"teams": {"data": [{"id": "00000000-da3a-0000-0000-000000000000", "type": "teams"}]}}, "type": "schedules"}}
+    And body with value {"data": {"attributes": {"layers": [{"effective_date": "2025-02-03T05:00:00Z", "end_date": "2025-12-31T00:00:00Z", "interval": {"seconds": 3600}, "members": [{"user": {"id": "00000000-aba1-0000-0000-000000000000"}}], "name": "Layer 1", "restrictions": [{"end_day": "friday", "end_time": "17:00:00", "start_day": "monday", "start_time": "09:00:00"}], "rotation_start": "2025-02-01T00:00:00Z"}], "name": "On-Call Schedule Updated", "time_zone": "America/New_York"}, "id": "3653d3c6-0c75-11ea-ad28-fb5701eabc7d", "relationships": {"teams": {"data": [{"id": "00000000-da3a-0000-0000-000000000000", "type": "teams"}]}}, "type": "schedules"}}
     When the request is sent
     Then the response status is 404 Not Found
 
@@ -240,6 +240,6 @@ Feature: On-Call
     And there is a valid "schedule" in the system
     And there is a valid "dd_team" in the system
     And request contains "schedule_id" parameter from "schedule.data.id"
-    And body with value {"data": { "id": "{{ schedule.data.id }}", "attributes": {"layers": [{"id": "{{ schedule.data.relationships.layers.data[0].id }}" , "effective_date": "{{ timeISO('now - 10d') }}", "end_date": "{{ timeISO('now + 10d') }}", "interval": {"seconds": 300}, "members": [{"user": {"id": "{{user.data.id}}"}}], "name": "Layer 1", "restrictions": [{"end_day": "friday", "end_time": "17:00:00", "start_day": "monday", "start_time": "09:00:00"}], "rotation_start": "{{ timeISO('now - 5d') }}"}], "name": "{{ unique }}", "time_zone": "America/New_York"}, "relationships": {"teams": {"data": [{"id": "{{dd_team.data.id}}", "type": "teams"}]}}, "type": "schedules"}}
+    And body with value {"data": { "id": "{{ schedule.data.id }}", "attributes": {"layers": [{"id": "{{ schedule.data.relationships.layers.data[0].id }}" , "effective_date": "{{ timeISO('now - 10d') }}", "end_date": "{{ timeISO('now + 10d') }}", "interval": {"seconds": 3600}, "members": [{"user": {"id": "{{user.data.id}}"}}], "name": "Layer 1", "restrictions": [{"end_day": "friday", "end_time": "17:00:00", "start_day": "monday", "start_time": "09:00:00"}], "rotation_start": "{{ timeISO('now - 5d') }}"}], "name": "{{ unique }}", "time_zone": "America/New_York"}, "relationships": {"teams": {"data": [{"id": "{{dd_team.data.id}}", "type": "teams"}]}}, "type": "schedules"}}
     When the request is sent
     Then the response status is 200 OK