Deprecate app_sec_spans datasource in SecurityMonitoringStandardDataSource#35293
Deprecate app_sec_spans datasource in SecurityMonitoringStandardDataSource#35293api-clients-generation-pipeline[bot] wants to merge 1 commit intomasterfrom
app_sec_spans datasource in SecurityMonitoringStandardDataSource#35293Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: e4adf4b761
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| tags: | ||
| - Reference Tables | ||
| x-menu-order: 10 | ||
| /api/v2/reference-tables/tables: |
There was a problem hiding this comment.
Re-add BatchRowsQuery endpoint to the v2 OpenAPI spec
This change removes the entire BatchRowsQuery operation (/api/v2/reference-tables/queries/batch-rows) from data/api/v2/full_spec.yaml, and also drops its menu/examples/translation entries, which means published API docs and generated clients will no longer expose that request path. Given the commit scope is deprecating app_sec_spans, this looks like an unintended rollback of an existing Reference Tables API and is a breaking docs/SDK regression for users relying on batch row lookup.
Useful? React with 👍 / 👎.
See DataDog/datadog-api-spec#5264 Test branch datadog-api-spec/test/tanguy.lichau/deprecate-app-sec-spans-datasource