Skip to content

Commit

Permalink
Regenerate client from commit 1ddbcdce of spec repo
Browse files Browse the repository at this point in the history
  • Loading branch information
ci.datadog-api-spec committed Oct 12, 2023
1 parent 9e7a7ef commit ef8b7f5
Show file tree
Hide file tree
Showing 5 changed files with 13 additions and 14 deletions.
8 changes: 4 additions & 4 deletions .apigentools-info
Original file line number Diff line number Diff line change
Expand Up @@ -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"
}
}
}
10 changes: 5 additions & 5 deletions .generator/schemas/v2/openapi.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Expand All @@ -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.

Expand Down Expand Up @@ -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.'
Expand Down
2 changes: 1 addition & 1 deletion src/datadog_api_client/v2/api/restriction_policies_api.py
Original file line number Diff line number Diff line change
Expand Up @@ -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.
"""

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -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]
Expand Down
5 changes: 2 additions & 3 deletions tests/v2/features/restriction_policies.feature
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down

0 comments on commit ef8b7f5

Please sign in to comment.