Update RestrictionPolicy docs with team and user support (#1570)

Co-authored-by: ci.datadog-api-spec <[email protected]>

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

.apigentools-info

@@ -4,13 +4,13 @@
     "spec_versions": {
         "v1": {
             "apigentools_version": "1.6.5",
-            "regenerated": "2023-07-10 14:43:41.796864",
-            "spec_repo_commit": "96fb94b8"
+            "regenerated": "2023-07-10 17:45:18.922571",
+            "spec_repo_commit": "9e0b471a"
         },
         "v2": {
             "apigentools_version": "1.6.5",
-            "regenerated": "2023-07-10 14:43:41.894242",
-            "spec_repo_commit": "96fb94b8"
+            "regenerated": "2023-07-10 17:45:18.934746",
+            "spec_repo_commit": "9e0b471a"
         }
     }
 }

.generator/schemas/v2/openapi.yaml

@@ -11679,19 +11679,23 @@ components:
           description: 'An array of principals. A principal is a subject or group
             of subjects.
 
-            Each principal is formatted as `type:id`. Supported types: `role` and
-            `org`.
+            Each principal is formatted as `type:id`. Supported types: `role`, `team`
+            (beta), `user` (beta), and `org`.
 
-            The org ID can be obtained through the api/v2/current_user API.'
+            The org ID can be obtained through the api/v2/current_user API.
+
+            The user principal type accepts service account IDs.'
           example:
           - role:00000000-0000-1111-0000-000000000000
           items:
             description: 'Subject or group of subjects. Each principal is formatted
               as `type:id`.
 
-              Supported types: `role` and `org`.
+              Supported types: `role`, `team` (beta), `user` (beta), and `org`.
+
+              The org ID can be obtained through the api/v2/current_user API.
 
-              The org ID can be obtained through the api/v2/current_user API.'
+              The user principal type accepts service account IDs.'
             type: string
           type: array
         relation:
@@ -27549,10 +27553,11 @@ tags:
 - description: 'A restriction policy defines the access control rules for a resource,
     mapping a set of relations
 
-    (such as editor and viewer) to a set of allowed principals (such as roles). The
-    restriction policy
+    (such as editor and viewer) to a set of allowed principals (such as roles, teams
+    (beta), or users (beta)).
 
-    determines who is authorized to perform what actions on the resource.'
+    The restriction policy determines who is authorized to perform what actions on
+    the resource.'
   name: Restriction Policies
 - description: 'The Roles API is used to create and manage Datadog roles, what
 

src/datadog_api_client/v2/api/restriction_policies_api.py

@@ -14,8 +14,8 @@
 class RestrictionPoliciesApi:
     """
     A restriction policy defines the access control rules for a resource, mapping a set of relations
-    (such as editor and viewer) to a set of allowed principals (such as roles). The restriction policy
-    determines who is authorized to perform what actions on the resource.
+    (such as editor and viewer) to a set of allowed principals (such as roles, teams (beta), or users (beta)).
+    The restriction policy determines who is authorized to perform what actions on the resource.
     """
 
     def __init__(self, api_client=None):

src/datadog_api_client/v2/model/restriction_policy_binding.py

@@ -29,8 +29,9 @@ def __init__(self_, principals: List[str], relation: str, **kwargs):
         Specifies which principals are associated with a relation.
 
         :param principals: An array of principals. A principal is a subject or group of subjects.
-            Each principal is formatted as ``type:id``. Supported types: ``role`` and ``org``.
+            Each principal is formatted as ``type:id``. Supported types: ``role`` , ``team`` (beta), ``user`` (beta), and ``org``.
             The org ID can be obtained through the api/v2/current_user API.
+            The user principal type accepts service account IDs.
         :type principals: [str]
 
         :param relation: The role/level of access.

tests/v2/features/restriction_policies.feature

@@ -2,8 +2,9 @@
 Feature: Restriction Policies
   A restriction policy defines the access control rules for a resource,
   mapping a set of relations (such as editor and viewer) to a set of allowed
-  principals (such as roles). The restriction policy determines who is
-  authorized to perform what actions on the resource.
+  principals (such as roles, teams (beta), or users (beta)). The restriction
+  policy determines who is authorized to perform what actions on the
+  resource.
 
   Background:
     Given a valid "apiKeyAuth" key in the system