Skip to content

Commit

Permalink
Regenerate client from commit 4b0e5500 of spec repo
Browse files Browse the repository at this point in the history
  • Loading branch information
ci.datadog-api-spec committed Oct 23, 2024
1 parent dc40d82 commit 9792086
Show file tree
Hide file tree
Showing 4 changed files with 40 additions and 40 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": "2024-10-23 10:08:16.626207",
"spec_repo_commit": "df3187ca"
"regenerated": "2024-10-23 14:05:14.280862",
"spec_repo_commit": "4b0e5500"
},
"v2": {
"apigentools_version": "1.6.6",
"regenerated": "2024-10-23 10:08:16.645066",
"spec_repo_commit": "df3187ca"
"regenerated": "2024-10-23 14:05:14.304423",
"spec_repo_commit": "4b0e5500"
}
}
}
Original file line number Diff line number Diff line change
@@ -1 +1 @@
"2022-05-12T09:52:59.418Z"
"2024-10-23T13:09:57.594Z"

Large diffs are not rendered by default.

4 changes: 2 additions & 2 deletions features/v2/roles.feature
Original file line number Diff line number Diff line change
Expand Up @@ -254,13 +254,13 @@ Feature: Roles
When the request is sent
Then the response status is 200 OK

@team:DataDog/aaa-core-access
@skip-validation @team:DataDog/aaa-core-access
Scenario: Revoke permission returns "Bad Request" response
Given there is a valid "role" in the system
And there is a valid "permission" in the system
And new "RemovePermissionFromRole" request
And request contains "role_id" parameter from "role.data.id"
And body with value {"data": {"id": "11111111-dead-beef-dead-ffffffffffff", "type": "{{ permission.type }}"}}
And body with value {"data": {"id": "11111111-dead-beef-dead-ffffffffffff", "type": "bad_permission_type"}}
When the request is sent
Then the response status is 400 Bad Request

Expand Down

0 comments on commit 9792086

Please sign in to comment.