Regenerate client from commit ecdb1e28 of spec repo

.apigentools-info

@@ -4,13 +4,13 @@
     "spec_versions": {
         "v1": {
             "apigentools_version": "1.6.6",
-            "regenerated": "2023-10-12 13:31:25.324384",
-            "spec_repo_commit": "6653b14d"
+            "regenerated": "2023-10-12 14:27:49.097291",
+            "spec_repo_commit": "ecdb1e28"
         },
         "v2": {
             "apigentools_version": "1.6.6",
-            "regenerated": "2023-10-12 13:31:25.363429",
-            "spec_repo_commit": "6653b14d"
+            "regenerated": "2023-10-12 14:27:49.111264",
+            "spec_repo_commit": "ecdb1e28"
         }
     }
 }

.generator/schemas/v2/openapi.yaml

@@ -12095,8 +12095,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.
 
@@ -12107,7 +12107,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.
 
@@ -29120,8 +29120,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.'

api/datadogV2/model_restriction_policy_binding.go

@@ -15,7 +15,7 @@ import (
 // RestrictionPolicyBinding Specifies which principals are associated with a relation.
 type RestrictionPolicyBinding struct {
 	// 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.
 	Principals []string `json:"principals"`

tests/scenarios/features/v2/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