Remove team and user beta tags from restriction policy API docs (#1719)

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.6",
-            "regenerated": "2023-10-12 17:29:36.397424",
-            "spec_repo_commit": "201be608"
+            "regenerated": "2023-10-12 18:33:22.507320",
+            "spec_repo_commit": "1ddbcdce"
         },
         "v2": {
             "apigentools_version": "1.6.6",
-            "regenerated": "2023-10-12 17:29:36.410797",
-            "spec_repo_commit": "201be608"
+            "regenerated": "2023-10-12 18:33:22.526135",
+            "spec_repo_commit": "1ddbcdce"
         }
     }
 }

.generator/schemas/v2/openapi.yaml

@@ -12405,8 +12405,8 @@ 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`, `team`
-            (beta), `user` (beta), and `org`.
+            Each principal is formatted as `type:id`. Supported types: `role`, `team`,
+            `user`, and `org`.
 
             The org ID can be obtained through the api/v2/current_user API.
 
@@ -12417,7 +12417,7 @@ components:
             description: 'Subject or group of subjects. Each principal is formatted
               as `type:id`.
 
-              Supported types: `role`, `team` (beta), `user` (beta), and `org`.
+              Supported types: `role`, `team`, `user`, and `org`.
 
               The org ID can be obtained through the api/v2/current_user API.
 
@@ -29513,8 +29513,8 @@ 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, teams
-    (beta), or users (beta)).
+    (such as editor and viewer) to a set of allowed principals (such as roles, teams,
+    or users).
 
     The restriction policy determines who is authorized to perform what actions on
     the resource.'

src/datadog_api_client/v2/api/restriction_policies_api.py

@@ -14,7 +14,7 @@
 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, teams (beta), or users (beta)).
+    (such as editor and viewer) to a set of allowed principals (such as roles, teams, or users).
     The restriction policy determines who is authorized to perform what actions on the resource.
     """
 

src/datadog_api_client/v2/model/restriction_policy_binding.py

@@ -29,7 +29,7 @@ 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`` , ``team`` (beta), ``user`` (beta), and ``org``.
+            Each principal is formatted as ``type:id``. Supported types: ``role`` , ``team`` , ``user`` , 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]

tests/v2/features/restriction_policies.feature

@@ -2,9 +2,8 @@
 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, teams (beta), or users (beta)). The restriction
-  policy determines who is authorized to perform what actions on the
-  resource.
+  principals (such as roles, teams, or users). The restriction policy
+  determines who is authorized to perform what actions on the resource.
 
   Background:
     Given a valid "apiKeyAuth" key in the system