Add partial hierarchy selection to team sync endpoints (#3060)

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

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

.generator/schemas/v2/openapi.yaml

@@ -65885,6 +65885,8 @@ components:
       properties:
         frequency:
           $ref: "#/components/schemas/TeamSyncAttributesFrequency"
+        selection_state:
+          $ref: "#/components/schemas/TeamSyncAttributesSelectionState"
         source:
           $ref: "#/components/schemas/TeamSyncAttributesSource"
         sync_membership:
@@ -65907,6 +65909,14 @@ components:
         - ONCE
         - CONTINUOUSLY
         - PAUSED
+    TeamSyncAttributesSelectionState:
+      description: |-
+        Specifies which teams or organizations to sync. When
+        provided, synchronization is limited to the specified
+        items and their subtrees.
+      items:
+        $ref: "#/components/schemas/TeamSyncSelectionStateItem"
+      type: array
     TeamSyncAttributesSource:
       description: The external source platform for team synchronization. Only "github" is supported.
       enum:
@@ -65916,6 +65926,7 @@ components:
       x-enum-varnames:
         - GITHUB
     TeamSyncAttributesSyncMembership:
+      default: false
       description: Whether to sync members from the external team to the Datadog team. Defaults to `false` when not provided.
       example: true
       type: boolean
@@ -65975,6 +65986,72 @@ components:
             $ref: "#/components/schemas/TeamSyncData"
           type: array
       type: object
+    TeamSyncSelectionStateExternalId:
+      description: The external identifier for a team or organization in the source platform.
+      properties:
+        type:
+          $ref: "#/components/schemas/TeamSyncSelectionStateExternalIdType"
+        value:
+          $ref: "#/components/schemas/TeamSyncSelectionStateExternalIdValue"
+      required:
+        - type
+        - value
+      type: object
+    TeamSyncSelectionStateExternalIdType:
+      description: |-
+        The type of external identifier for the selection state item.
+        For GitHub synchronization, the allowed values are `team` and
+        `organization`.
+      enum:
+        - team
+        - organization
+      example: team
+      type: string
+      x-enum-varnames:
+        - TEAM
+        - ORGANIZATION
+    TeamSyncSelectionStateExternalIdValue:
+      description: |-
+        The external identifier value from the source
+        platform. For GitHub, this is the string
+        representation of a GitHub organization ID or team
+        ID.
+      example: "1"
+      type: string
+    TeamSyncSelectionStateItem:
+      description: Identifies a team or organization hierarchy to include in synchronization.
+      properties:
+        external_id:
+          $ref: "#/components/schemas/TeamSyncSelectionStateExternalId"
+        operation:
+          $ref: "#/components/schemas/TeamSyncSelectionStateOperation"
+        scope:
+          $ref: "#/components/schemas/TeamSyncSelectionStateScope"
+      required:
+        - external_id
+      type: object
+    TeamSyncSelectionStateOperation:
+      description: |-
+        The operation to perform on the selected hierarchy.
+        When set to `include`, synchronization covers the
+        referenced teams or organizations.
+      enum:
+        - include
+      example: include
+      type: string
+      x-enum-varnames:
+        - INCLUDE
+    TeamSyncSelectionStateScope:
+      description: |-
+        The scope of the selection. When set to `subtree`,
+        synchronization includes the referenced team or
+        organization and everything nested under it.
+      enum:
+        - subtree
+      example: subtree
+      type: string
+      x-enum-varnames:
+        - SUBTREE
     TeamTarget:
       description: "Represents a team target for an escalation policy step, including the team's ID and resource type."
       properties:
@@ -105434,12 +105511,6 @@ paths:
           description: OK
         "403":
           $ref: "#/components/responses/ForbiddenResponse"
-        "404":
-          content:
-            application/json:
-              schema:
-                $ref: "#/components/schemas/APIErrorResponse"
-          description: Team sync configurations not found
         "429":
           $ref: "#/components/responses/TooManyRequestsResponse"
       security:
@@ -105456,13 +105527,17 @@ paths:
           - teams_read
     post:
       description: |-
-        This endpoint attempts to link your existing Datadog teams with GitHub teams by matching their names.
+        This endpoint configures synchronization between your existing Datadog teams and GitHub teams by matching their names.
         It evaluates all current Datadog teams and compares them against teams in the GitHub organization
         connected to your Datadog account, based on Datadog Team handle and GitHub Team slug
         (lowercased and kebab-cased).
 
         This operation is read-only on the GitHub side, no teams will be modified or created.
 
+        Optionally, provide `selection_state` to limit synchronization
+        to specific teams or organizations and their subtrees, instead
+        of syncing all teams.
+
         [A GitHub organization must be connected to your Datadog account](https://docs.datadoghq.com/integrations/github/),
         and the GitHub App integrated with Datadog must have the `Members Read` permission. Matching is performed by comparing the Datadog team handle to the GitHub team slug
         using a normalized exact match; case is ignored and spaces are removed. No modifications are made
@@ -105477,6 +105552,8 @@ paths:
       responses:
         "200":
           description: OK
+        "204":
+          description: No Content
         "403":
           $ref: "#/components/responses/ForbiddenResponse"
         "429":

cassettes/features/v2/teams/Get-team-sync-configurations-returns-OK-response.frozen

@@ -0,0 +1 @@
+2026-03-04T16:01:00.945Z

cassettes/features/v2/teams/Get-team-sync-configurations-returns-OK-response.yml

@@ -0,0 +1 @@
+2026-03-04T16:01:34.366Z

cassettes/features/v2/teams/Link-Teams-with-GitHub-Teams-returns-No-Content-response.frozen

@@ -431,20 +431,13 @@ Feature: Teams
     Then the response status is 200 OK
     And the response "data" has length 1
 
-  @generated @skip @team:DataDog/aaa-omg
+  @team:DataDog/aaa-omg
   Scenario: Get team sync configurations returns "OK" response
     Given new "GetTeamSync" request
-    And request contains "filter[source]" parameter from "REPLACE.ME"
+    And request contains "filter[source]" parameter with value "github"
     When the request is sent
     Then the response status is 200 OK
 
-  @generated @skip @team:DataDog/aaa-omg
-  Scenario: Get team sync configurations returns "Team sync configurations not found" response
-    Given new "GetTeamSync" request
-    And request contains "filter[source]" parameter from "REPLACE.ME"
-    When the request is sent
-    Then the response status is 404 Team sync configurations not found
-
   @generated @skip @team:DataDog/aaa-omg
   Scenario: Get user memberships returns "API error response." response
     Given new "GetUserMemberships" request
@@ -461,6 +454,13 @@ Feature: Teams
     Then the response status is 200 Represents a user's association to a team
     And the response "data" has length 0
 
+  @team:DataDog/aaa-omg
+  Scenario: Link Teams with GitHub Teams returns "No Content" response
+    Given new "SyncTeams" request
+    And body with value {"data": {"attributes": {"source": "github", "type": "link", "selection_state": [{"external_id": {"type": "organization", "value": "1"}}]}, "type": "team_sync_bulk"}}
+    When the request is sent
+    Then the response status is 204 No Content
+
   @generated @skip @team:DataDog/aaa-omg
   Scenario: Link Teams with GitHub Teams returns "OK" response
     Given new "SyncTeams" request
@@ -582,13 +582,6 @@ Feature: Teams
     When the request is sent
     Then the response status is 204 No Content
 
-  @replay-only @team:DataDog/aaa-omg
-  Scenario: Sync teams returns "OK" response
-    Given new "SyncTeams" request
-    And body with value {"data": {"attributes": {"source": "github", "type": "link"}, "type": "team_sync_bulk"}}
-    When the request is sent
-    Then the response status is 200 OK
-
   @team:DataDog/aaa-omg
   Scenario: Update a team link returns "API error response." response
     Given new "UpdateTeamLink" request

…teams/Sync-teams-returns-OK-response.yml …ub-Teams-returns-No-Content-response.ymlcassettes/features/v2/teams/Sync-teams-returns-OK-response.yml renamed to cassettes/features/v2/teams/Link-Teams-with-GitHub-Teams-returns-No-Content-response.yml cassettes/features/v2/teams/Sync-teams-returns-OK-response.yml renamed to cassettes/features/v2/teams/Link-Teams-with-GitHub-Teams-returns-No-Content-response.yml

@@ -5343,6 +5343,11 @@ def overrides
           "v2.team_sync_data" => "TeamSyncData",
           "v2.team_sync_request" => "TeamSyncRequest",
           "v2.team_sync_response" => "TeamSyncResponse",
+          "v2.team_sync_selection_state_external_id" => "TeamSyncSelectionStateExternalId",
+          "v2.team_sync_selection_state_external_id_type" => "TeamSyncSelectionStateExternalIdType",
+          "v2.team_sync_selection_state_item" => "TeamSyncSelectionStateItem",
+          "v2.team_sync_selection_state_operation" => "TeamSyncSelectionStateOperation",
+          "v2.team_sync_selection_state_scope" => "TeamSyncSelectionStateScope",
           "v2.team_target" => "TeamTarget",
           "v2.team_target_type" => "TeamTargetType",
           "v2.team_type" => "TeamType",

cassettes/features/v2/teams/Sync-teams-returns-OK-response.frozen

@@ -2107,13 +2107,17 @@ def sync_teams(body, opts = {})
 
     # Link Teams with GitHub Teams.
     #
-    # This endpoint attempts to link your existing Datadog teams with GitHub teams by matching their names.
+    # This endpoint configures synchronization between your existing Datadog teams and GitHub teams by matching their names.
     # It evaluates all current Datadog teams and compares them against teams in the GitHub organization
     # connected to your Datadog account, based on Datadog Team handle and GitHub Team slug
     # (lowercased and kebab-cased).
     #
     # This operation is read-only on the GitHub side, no teams will be modified or created.
     #
+    # Optionally, provide `selection_state` to limit synchronization
+    # to specific teams or organizations and their subtrees, instead
+    # of syncing all teams.
+    #
     # [A GitHub organization must be connected to your Datadog account](https://docs.datadoghq.com/integrations/github/),
     # and the GitHub App integrated with Datadog must have the `Members Read` permission. Matching is performed by comparing the Datadog team handle to the GitHub team slug
     # using a normalized exact match; case is ignored and spaces are removed. No modifications are made