Skip to content

fix: replace invalid team 'api-management' with 'apm-aoe' in CODEOWNERS #3295

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
api-clients-generation-pipeline merged 1 commit into from
Mar 12, 2026
Merged

fix: replace invalid team 'api-management' with 'apm-aoe' in CODEOWNERS #3295

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
26 changes: 13 additions & 13 deletions tests/v2/features/api_management.feature
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ Feature: API Management
And a valid "appKeyAuth" key in the system
And an instance of "APIManagement" API

@integration-only @skip-terraform-config @skip-validation @team:DataDog/api-management
@integration-only @skip-terraform-config @skip-validation @team:DataDog/apm-aoe
Scenario: Create a new API returns "API created successfully" response
Given operation "CreateOpenAPI" enabled
And new "CreateOpenAPI" request
Expand All @@ -16,14 +16,14 @@ Feature: API Management
Then the response status is 201 API created successfully
And the response "data.attributes.failed_endpoints" has length 0

@generated @skip @team:DataDog/api-management
@generated @skip @team:DataDog/apm-aoe
Scenario: Create a new API returns "Bad request" response
Given operation "CreateOpenAPI" enabled
And new "CreateOpenAPI" request
When the request is sent
Then the response status is 400 Bad request

@integration-only @skip-terraform-config @skip-validation @team:DataDog/api-management
@integration-only @skip-terraform-config @skip-validation @team:DataDog/apm-aoe
Scenario: Delete an API returns "API deleted successfully" response
Given operation "DeleteOpenAPI" enabled
And there is a valid "managed_api" in the system
Expand All @@ -32,39 +32,39 @@ Feature: API Management
When the request is sent
Then the response status is 204 API deleted successfully

@generated @skip @team:DataDog/api-management
@generated @skip @team:DataDog/apm-aoe
Scenario: Delete an API returns "API not found error" response
Given operation "DeleteOpenAPI" enabled
And new "DeleteOpenAPI" request
And request contains "id" parameter from "REPLACE.ME"
When the request is sent
Then the response status is 404 API not found error

@generated @skip @team:DataDog/api-management
@generated @skip @team:DataDog/apm-aoe
Scenario: Delete an API returns "Bad request" response
Given operation "DeleteOpenAPI" enabled
And new "DeleteOpenAPI" request
And request contains "id" parameter from "REPLACE.ME"
When the request is sent
Then the response status is 400 Bad request

@generated @skip @team:DataDog/api-management
@generated @skip @team:DataDog/apm-aoe
Scenario: Get an API returns "API not found error" response
Given operation "GetOpenAPI" enabled
And new "GetOpenAPI" request
And request contains "id" parameter from "REPLACE.ME"
When the request is sent
Then the response status is 404 API not found error

@generated @skip @team:DataDog/api-management
@generated @skip @team:DataDog/apm-aoe
Scenario: Get an API returns "Bad request" response
Given operation "GetOpenAPI" enabled
And new "GetOpenAPI" request
And request contains "id" parameter from "REPLACE.ME"
When the request is sent
Then the response status is 400 Bad request

@integration-only @skip-terraform-config @skip-validation @team:DataDog/api-management
@integration-only @skip-terraform-config @skip-validation @team:DataDog/apm-aoe
Scenario: Get an API returns "OK" response
Given operation "GetOpenAPI" enabled
And there is a valid "managed_api" in the system
Expand All @@ -73,29 +73,29 @@ Feature: API Management
When the request is sent
Then the response status is 200 OK

@generated @skip @team:DataDog/api-management
@generated @skip @team:DataDog/apm-aoe
Scenario: List APIs returns "Bad request" response
Given operation "ListAPIs" enabled
And new "ListAPIs" request
When the request is sent
Then the response status is 400 Bad request

@generated @skip @team:DataDog/api-management
@generated @skip @team:DataDog/apm-aoe
Scenario: List APIs returns "OK" response
Given operation "ListAPIs" enabled
And new "ListAPIs" request
When the request is sent
Then the response status is 200 OK

@generated @skip @team:DataDog/api-management
@generated @skip @team:DataDog/apm-aoe
Scenario: Update an API returns "API not found error" response
Given operation "UpdateOpenAPI" enabled
And new "UpdateOpenAPI" request
And request contains "id" parameter from "REPLACE.ME"
When the request is sent
Then the response status is 404 API not found error

@integration-only @skip-terraform-config @skip-validation @team:DataDog/api-management
@integration-only @skip-terraform-config @skip-validation @team:DataDog/apm-aoe
Scenario: Update an API returns "API updated successfully" response
Given operation "UpdateOpenAPI" enabled
And there is a valid "managed_api" in the system
Expand All @@ -106,7 +106,7 @@ Feature: API Management
Then the response status is 200 API updated successfully
And the response "data.attributes.failed_endpoints" has length 0

@generated @skip @team:DataDog/api-management
@generated @skip @team:DataDog/apm-aoe
Scenario: Update an API returns "Bad request" response
Given operation "UpdateOpenAPI" enabled
And new "UpdateOpenAPI" request
Expand Down
Loading