Skip to content

Remove unstable tags from Case Management APIs #4676

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
Jul 22, 2026
Merged

Remove unstable tags from Case Management APIs #4676

Show file tree
Hide file tree
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
129 changes: 0 additions & 129 deletions .generator/schemas/v2/openapi.yaml
View file
Open in desktop

Large diffs are not rendered by default.

369 changes: 123 additions & 246 deletions features/v2/case_management.feature
View file
Open in desktop

Large diffs are not rendered by default.

9 changes: 3 additions & 6 deletions features/v2/case_management_attribute.feature
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -78,8 +78,7 @@ Feature: Case Management Attribute

@generated @skip @team:DataDog/case-management
Scenario: Update custom attribute config returns "Bad Request" response
Given operation "UpdateCustomAttributeConfig" enabled
And new "UpdateCustomAttributeConfig" request
Given new "UpdateCustomAttributeConfig" request
And request contains "case_type_id" parameter from "REPLACE.ME"
And request contains "custom_attribute_id" parameter from "REPLACE.ME"
And body with value {"data": {"attributes": {"description": "Updated description.", "display_name": "AWS Region", "type": "NUMBER", "type_data": {"options": [{"value": "us-east-1"}]}}, "type": "custom_attribute"}}
Expand All @@ -88,8 +87,7 @@ Feature: Case Management Attribute

@generated @skip @team:DataDog/case-management
Scenario: Update custom attribute config returns "Not Found" response
Given operation "UpdateCustomAttributeConfig" enabled
And new "UpdateCustomAttributeConfig" request
Given new "UpdateCustomAttributeConfig" request
And request contains "case_type_id" parameter from "REPLACE.ME"
And request contains "custom_attribute_id" parameter from "REPLACE.ME"
And body with value {"data": {"attributes": {"description": "Updated description.", "display_name": "AWS Region", "type": "NUMBER", "type_data": {"options": [{"value": "us-east-1"}]}}, "type": "custom_attribute"}}
Expand All @@ -98,8 +96,7 @@ Feature: Case Management Attribute

@generated @skip @team:DataDog/case-management
Scenario: Update custom attribute config returns "OK" response
Given operation "UpdateCustomAttributeConfig" enabled
And new "UpdateCustomAttributeConfig" request
Given new "UpdateCustomAttributeConfig" request
And request contains "case_type_id" parameter from "REPLACE.ME"
And request contains "custom_attribute_id" parameter from "REPLACE.ME"
And body with value {"data": {"attributes": {"description": "Updated description.", "display_name": "AWS Region", "type": "NUMBER", "type_data": {"options": [{"value": "us-east-1"}]}}, "type": "custom_attribute"}}
Expand Down
9 changes: 3 additions & 6 deletions features/v2/case_management_type.feature
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -47,26 +47,23 @@ Feature: Case Management Type

@generated @skip @team:DataDog/case-management
Scenario: Update a case type returns "Bad Request" response
Given operation "UpdateCaseType" enabled
And new "UpdateCaseType" request
Given new "UpdateCaseType" request
And request contains "case_type_id" parameter from "REPLACE.ME"
And body with value {"data": {"attributes": {"description": "Investigations done in case management", "emoji": "\ud83d\udd75\ud83c\udffb\u200d\u2642\ufe0f", "name": "Investigation"}, "type": "case_type"}}
When the request is sent
Then the response status is 400 Bad Request

@generated @skip @team:DataDog/case-management
Scenario: Update a case type returns "Not Found" response
Given operation "UpdateCaseType" enabled
And new "UpdateCaseType" request
Given new "UpdateCaseType" request
And request contains "case_type_id" parameter from "REPLACE.ME"
And body with value {"data": {"attributes": {"description": "Investigations done in case management", "emoji": "\ud83d\udd75\ud83c\udffb\u200d\u2642\ufe0f", "name": "Investigation"}, "type": "case_type"}}
When the request is sent
Then the response status is 404 Not Found

@generated @skip @team:DataDog/case-management
Scenario: Update a case type returns "OK" response
Given operation "UpdateCaseType" enabled
And new "UpdateCaseType" request
Given new "UpdateCaseType" request
And request contains "case_type_id" parameter from "REPLACE.ME"
And body with value {"data": {"attributes": {"description": "Investigations done in case management", "emoji": "\ud83d\udd75\ud83c\udffb\u200d\u2642\ufe0f", "name": "Investigation"}, "type": "case_type"}}
When the request is sent
Expand Down
Loading
Loading