Skip to content

Conversation

@api-clients-generation-pipeline
Copy link
Contributor

@datadog-official
Copy link

datadog-official bot commented Dec 18, 2025

⚠️ Tests

Fix all issues with Cursor

⚠️ Warnings

🧪 36 Tests failed

    Create a new pipeline returns "Bad Request" response from Observability Pipelines at features/v2/observability_pipelines.feature (Fix with Cursor)

    Create a new pipeline returns "Bad Request" response from Observability Pipelines at features/v2/observability_pipelines.feature (Fix with Cursor)

Create a new pipeline returns "Bad Request" response from Observability Pipelines at features/v2/observability_pipelines.feature (Datadog) (Fix with Cursor)
There are unused HTTP interactions left in the cassette:
  - [post https://api.datadoghq.com/api/v2/remote_config/products/obs_pipelines/pipelines] => [400 "{\"errors\":[{\"title\":\"Component with ID my-processor-group is an unknown componen"]
View all

ℹ️ Info

❄️ No new flaky tests detected

This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 79aefb8 | Docs | Datadog PR Page | Was this helpful? Give us feedback!

@api-clients-generation-pipeline api-clients-generation-pipeline bot force-pushed the datadog-api-spec/generated/4719 branch 3 times, most recently from 166b5bb to 9b1a4aa Compare December 22, 2025 11:07
@api-clients-generation-pipeline api-clients-generation-pipeline bot force-pushed the datadog-api-spec/generated/4719 branch from 9b1a4aa to 79aefb8 Compare December 22, 2025 11:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant