From 1974109f5549b756ff31449bd60abb94290f9109 Mon Sep 17 00:00:00 2001 From: "ci.datadog-api-spec" Date: Mon, 18 Aug 2025 20:34:00 +0000 Subject: [PATCH] Regenerate client from commit fde8b90 of spec repo --- .generated-info | 4 +-- .../api/client/v2/api/authn_mappings.feature | 26 +++++++++---------- 2 files changed, 15 insertions(+), 15 deletions(-) diff --git a/.generated-info b/.generated-info index bb6b1b323ba..e93d3fbdb80 100644 --- a/.generated-info +++ b/.generated-info @@ -1,4 +1,4 @@ { - "spec_repo_commit": "7851858", - "generated": "2025-08-18 14:49:09.895" + "spec_repo_commit": "fde8b90", + "generated": "2025-08-18 20:34:00.694" } diff --git a/src/test/resources/com/datadog/api/client/v2/api/authn_mappings.feature b/src/test/resources/com/datadog/api/client/v2/api/authn_mappings.feature index a90c3e6adef..9e0bb72fec8 100644 --- a/src/test/resources/com/datadog/api/client/v2/api/authn_mappings.feature +++ b/src/test/resources/com/datadog/api/client/v2/api/authn_mappings.feature @@ -10,21 +10,21 @@ Feature: AuthN Mappings And a valid "appKeyAuth" key in the system And an instance of "AuthNMappings" API - @generated @skip @team:DataDog/aaa-core-access + @generated @skip @team:DataDog/team-aaa-identity Scenario: Create an AuthN Mapping returns "Bad Request" response Given new "CreateAuthNMapping" request And body with value {"data": {"attributes": {"attribute_key": "member-of", "attribute_value": "Development"}, "relationships": {"role": {"data": {"id": "3653d3c6-0c75-11ea-ad28-fb5701eabc7d", "type": "roles"}}}, "type": "authn_mappings"}} When the request is sent Then the response status is 400 Bad Request - @generated @skip @team:DataDog/aaa-core-access + @generated @skip @team:DataDog/team-aaa-identity Scenario: Create an AuthN Mapping returns "Not Found" response Given new "CreateAuthNMapping" request And body with value {"data": {"attributes": {"attribute_key": "member-of", "attribute_value": "Development"}, "relationships": {"role": {"data": {"id": "3653d3c6-0c75-11ea-ad28-fb5701eabc7d", "type": "roles"}}}, "type": "authn_mappings"}} When the request is sent Then the response status is 404 Not Found - @team:DataDog/aaa-core-access + @team:DataDog/team-aaa-identity Scenario: Create an AuthN Mapping returns "OK" response Given there is a valid "role" in the system And new "CreateAuthNMapping" request @@ -35,14 +35,14 @@ Feature: AuthN Mappings And the response "data.attributes.attribute_value" is equal to "{{ unique }}" And the response "data.relationships.role.data.id" is equal to "{{ role.data.id }}" - @generated @skip @team:DataDog/aaa-core-access + @generated @skip @team:DataDog/team-aaa-identity Scenario: Delete an AuthN Mapping returns "Not Found" response Given new "DeleteAuthNMapping" request And request contains "authn_mapping_id" parameter from "REPLACE.ME" When the request is sent Then the response status is 404 Not Found - @team:DataDog/aaa-core-access + @team:DataDog/team-aaa-identity Scenario: Delete an AuthN Mapping returns "OK" response Given there is a valid "role" in the system And there is a valid "authn_mapping" in the system @@ -51,7 +51,7 @@ Feature: AuthN Mappings When the request is sent Then the response status is 204 OK - @generated @skip @team:DataDog/aaa-core-access + @generated @skip @team:DataDog/team-aaa-identity Scenario: Edit an AuthN Mapping returns "Bad Request" response Given new "UpdateAuthNMapping" request And request contains "authn_mapping_id" parameter from "REPLACE.ME" @@ -59,7 +59,7 @@ Feature: AuthN Mappings When the request is sent Then the response status is 400 Bad Request - @generated @skip @team:DataDog/aaa-core-access + @generated @skip @team:DataDog/team-aaa-identity Scenario: Edit an AuthN Mapping returns "Conflict" response Given new "UpdateAuthNMapping" request And request contains "authn_mapping_id" parameter from "REPLACE.ME" @@ -67,7 +67,7 @@ Feature: AuthN Mappings When the request is sent Then the response status is 409 Conflict - @generated @skip @team:DataDog/aaa-core-access + @generated @skip @team:DataDog/team-aaa-identity Scenario: Edit an AuthN Mapping returns "Not Found" response Given new "UpdateAuthNMapping" request And request contains "authn_mapping_id" parameter from "REPLACE.ME" @@ -75,7 +75,7 @@ Feature: AuthN Mappings When the request is sent Then the response status is 404 Not Found - @team:DataDog/aaa-core-access + @team:DataDog/team-aaa-identity Scenario: Edit an AuthN Mapping returns "OK" response Given there is a valid "role" in the system And there is a valid "authn_mapping" in the system @@ -89,7 +89,7 @@ Feature: AuthN Mappings And the response "data.attributes.attribute_value" is equal to "Development" And the response "data.relationships.role.data.id" is equal to "{{ role.data.id }}" - @generated @skip @team:DataDog/aaa-core-access + @generated @skip @team:DataDog/team-aaa-identity Scenario: Edit an AuthN Mapping returns "Unprocessable Entity" response Given new "UpdateAuthNMapping" request And request contains "authn_mapping_id" parameter from "REPLACE.ME" @@ -97,14 +97,14 @@ Feature: AuthN Mappings When the request is sent Then the response status is 422 Unprocessable Entity - @generated @skip @team:DataDog/aaa-core-access + @generated @skip @team:DataDog/team-aaa-identity Scenario: Get an AuthN Mapping by UUID returns "Not Found" response Given new "GetAuthNMapping" request And request contains "authn_mapping_id" parameter from "REPLACE.ME" When the request is sent Then the response status is 404 Not Found - @team:DataDog/aaa-core-access + @team:DataDog/team-aaa-identity Scenario: Get an AuthN Mapping by UUID returns "OK" response Given there is a valid "role" in the system And there is a valid "authn_mapping" in the system @@ -117,7 +117,7 @@ Feature: AuthN Mappings And the response "data.attributes.attribute_value" is equal to "{{ unique }}" And the response "data.relationships.role.data.id" is equal to "{{ role.data.id }}" - @team:DataDog/aaa-core-access + @team:DataDog/team-aaa-identity Scenario: List all AuthN Mappings returns "OK" response Given there is a valid "role" in the system And there is a valid "authn_mapping" in the system