Skip to content

Add 409 response to unarchive feature flag #3890

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

Open
api-clients-generation-pipeline wants to merge 1 commit into
base: master
Choose a base branch
from
+13 −0
Open

Add 409 response to unarchive feature flag #3890

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
6 changes: 6 additions & 0 deletions .generator/schemas/v2/openapi.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -143806,6 +143806,12 @@ paths:
schema:
$ref: "#/components/schemas/APIErrorResponse"
description: Not Found
"409":
content:
application/json:
schema:
$ref: "#/components/schemas/APIErrorResponse"
description: Conflict - Another active feature flag already uses the archived flag's key or name.
"429":
$ref: "#/components/responses/TooManyRequestsResponse"
security:
Expand Down
7 changes: 7 additions & 0 deletions tests/v2/features/feature_flags.feature
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -430,6 +430,13 @@ Feature: Feature Flags
When the request is sent
Then the response status is 400 Bad Request

@generated @skip @team:DataDog/feature-flags
Scenario: Unarchive a feature flag returns "Conflict - Another active feature flag already uses the archived flag's key or name." response
Given new "UnarchiveFeatureFlag" request
And request contains "feature_flag_id" parameter from "REPLACE.ME"
When the request is sent
Then the response status is 409 Conflict - Another active feature flag already uses the archived flag's key or name.

@skip @team:DataDog/feature-flags
Scenario: Unarchive a feature flag returns "Not Found" response
Given new "UnarchiveFeatureFlag" request
Expand Down
Loading