Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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
24 changes: 24 additions & 0 deletions .generator/schemas/v1/openapi.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -36328,6 +36328,12 @@ paths:
schema:
$ref: "#/components/schemas/APIErrorResponse"
description: Forbidden
"409":
content:
application/json:
schema:
$ref: "#/components/schemas/LogsAPIErrorResponse"
description: Conflict
"422":
content:
application/json:
Expand Down Expand Up @@ -36429,6 +36435,12 @@ paths:
schema:
$ref: "#/components/schemas/APIErrorResponse"
description: Forbidden
"409":
content:
application/json:
schema:
$ref: "#/components/schemas/LogsAPIErrorResponse"
description: Conflict
"429":
$ref: "#/components/responses/TooManyRequestsResponse"
summary: Create a pipeline
Expand Down Expand Up @@ -36467,6 +36479,12 @@ paths:
schema:
$ref: "#/components/schemas/APIErrorResponse"
description: Forbidden
"409":
content:
application/json:
schema:
$ref: "#/components/schemas/LogsAPIErrorResponse"
description: Conflict
"429":
$ref: "#/components/responses/TooManyRequestsResponse"
summary: Delete a pipeline
Expand Down Expand Up @@ -36584,6 +36602,12 @@ paths:
schema:
$ref: "#/components/schemas/APIErrorResponse"
description: Forbidden
"409":
content:
application/json:
schema:
$ref: "#/components/schemas/LogsAPIErrorResponse"
description: Conflict
"429":
$ref: "#/components/responses/TooManyRequestsResponse"
summary: Update a pipeline
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -87,6 +87,7 @@ public CompletableFuture<LogsPipeline> createLogsPipelineAsync(LogsPipeline body
* <tr><td> 200 </td><td> OK </td><td> - </td></tr>
* <tr><td> 400 </td><td> Bad Request </td><td> - </td></tr>
* <tr><td> 403 </td><td> Forbidden </td><td> - </td></tr>
* <tr><td> 409 </td><td> Conflict </td><td> - </td></tr>
* <tr><td> 429 </td><td> Too many requests </td><td> - </td></tr>
* </table>
*/
Expand Down Expand Up @@ -217,6 +218,7 @@ public CompletableFuture<Void> deleteLogsPipelineAsync(String pipelineId) {
* <tr><td> 200 </td><td> OK </td><td> - </td></tr>
* <tr><td> 400 </td><td> Bad Request </td><td> - </td></tr>
* <tr><td> 403 </td><td> Forbidden </td><td> - </td></tr>
* <tr><td> 409 </td><td> Conflict </td><td> - </td></tr>
* <tr><td> 429 </td><td> Too many requests </td><td> - </td></tr>
* </table>
*/
Expand Down Expand Up @@ -717,6 +719,7 @@ public CompletableFuture<LogsPipeline> updateLogsPipelineAsync(
* <tr><td> 200 </td><td> OK </td><td> - </td></tr>
* <tr><td> 400 </td><td> Bad Request </td><td> - </td></tr>
* <tr><td> 403 </td><td> Forbidden </td><td> - </td></tr>
* <tr><td> 409 </td><td> Conflict </td><td> - </td></tr>
* <tr><td> 429 </td><td> Too many requests </td><td> - </td></tr>
* </table>
*/
Expand Down Expand Up @@ -876,6 +879,7 @@ public CompletableFuture<LogsPipelinesOrder> updateLogsPipelineOrderAsync(
* <tr><td> 200 </td><td> OK </td><td> - </td></tr>
* <tr><td> 400 </td><td> Bad Request </td><td> - </td></tr>
* <tr><td> 403 </td><td> Forbidden </td><td> - </td></tr>
* <tr><td> 409 </td><td> Conflict </td><td> - </td></tr>
* <tr><td> 422 </td><td> Unprocessable Entity </td><td> - </td></tr>
* <tr><td> 429 </td><td> Too many requests </td><td> - </td></tr>
* </table>
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -28,6 +28,13 @@ Feature: Logs Pipelines
When the request is sent
Then the response status is 400 Bad Request

@generated @skip @team:ddoghq/logs-onboarding
Scenario: Create a pipeline returns "Conflict" response
Given new "CreateLogsPipeline" request
And body with value {"filter": {"query": "source:python"}, "name": "", "processors": [{"grok": {"match_rules": "rule_name_1 foo\nrule_name_2 bar", "support_rules": "rule_name_1 foo\nrule_name_2 bar"}, "is_enabled": false, "samples": [], "source": "message", "type": "grok-parser"}], "tags": []}
When the request is sent
Then the response status is 409 Conflict

@generated @skip @team:ddoghq/logs-onboarding
Scenario: Create a pipeline returns "OK" response
Given new "CreateLogsPipeline" request
Expand Down Expand Up @@ -161,6 +168,13 @@ Feature: Logs Pipelines
When the request is sent
Then the response status is 400 Bad Request

@generated @skip @team:ddoghq/logs-onboarding
Scenario: Delete a pipeline returns "Conflict" response
Given new "DeleteLogsPipeline" request
And request contains "pipeline_id" parameter from "REPLACE.ME"
When the request is sent
Then the response status is 409 Conflict

@generated @skip @team:ddoghq/logs-onboarding
Scenario: Delete a pipeline returns "OK" response
Given new "DeleteLogsPipeline" request
Expand Down Expand Up @@ -202,6 +216,14 @@ Feature: Logs Pipelines
When the request is sent
Then the response status is 400 Bad Request

@generated @skip @team:ddoghq/logs-onboarding
Scenario: Update a pipeline returns "Conflict" response
Given new "UpdateLogsPipeline" request
And request contains "pipeline_id" parameter from "REPLACE.ME"
And body with value {"filter": {"query": "source:python"}, "name": "", "processors": [{"grok": {"match_rules": "rule_name_1 foo\nrule_name_2 bar", "support_rules": "rule_name_1 foo\nrule_name_2 bar"}, "is_enabled": false, "samples": [], "source": "message", "type": "grok-parser"}], "tags": []}
When the request is sent
Then the response status is 409 Conflict

@generated @skip @team:ddoghq/logs-onboarding
Scenario: Update a pipeline returns "OK" response
Given new "UpdateLogsPipeline" request
Expand All @@ -217,6 +239,13 @@ Feature: Logs Pipelines
When the request is sent
Then the response status is 400 Bad Request

@generated @skip @team:ddoghq/logs-onboarding
Scenario: Update pipeline order returns "Conflict" response
Given new "UpdateLogsPipelineOrder" request
And body with value {"pipeline_ids": ["tags", "org_ids", "products"]}
When the request is sent
Then the response status is 409 Conflict

@generated @skip @team:ddoghq/logs-onboarding
Scenario: Update pipeline order returns "OK" response
Given new "UpdateLogsPipelineOrder" request
Expand Down
Loading