Skip to content

Add HTTP 401/403 for endpoints with security field #2392

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.

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
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

@datadog-datadog-prod-us1
Copy link

datadog-datadog-prod-us1 bot commented May 6, 2025

Datadog Report

Branch report: datadog-api-spec/generated/3857
Commit report: 59f5cfd
Test service: datadog-api-client-ruby

❌ 140 Failed (47 Known Flaky), 360 Passed, 1764 Skipped, 2m 11.53s Total duration (20.1s time saved)

❌ Failed Tests (140)

This report shows up to 5 failed tests.

  • Get all custom metrics by hourly average returns "Bad Request" response - Usage Metering at features/v1/usage_metering.feature

  • Get all custom metrics by hourly average returns "Bad Request" response - Usage Metering at features/v1/usage_metering.feature

  • Get all custom metrics by hourly average returns "OK" response - Usage Metering at features/v1/usage_metering.feature

  • Get all custom metrics by hourly average returns "OK" response - Usage Metering at features/v1/usage_metering.feature - Details

    Expand for error
     There are unused HTTP interactions left in the cassette:
       - [get https://api.datadoghq.com/api/v1/usage/top_avg_metrics?day=2022-03-29T00%3A41%3A20.876Z] => [200 "{\"usage\":[{\"metric_category\":\"custom\",\"metric_name\":\"page.views\",\"max_metric_hou"]
    
  • Get hourly logs usage by retention returns "Bad Request" response - Usage Metering at features/v1/usage_metering.feature - ❄️ Known flaky

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.

0 participants