[APPSEC-61743] Add missing WAF addresses to custom rule public API#35299
[APPSEC-61743] Add missing WAF addresses to custom rule public API#35299api-clients-generation-pipeline[bot] wants to merge 1 commit intomasterfrom
Conversation
api-clients-generation-pipeline
bot
requested a review
from a team
as a code owner
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 4ba5acfed0
ℹ️ 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.
This change removes the /api/v2/reference-tables/queries/batch-rows operation (BatchRowsQuery) from data/api/v2/full_spec.yaml and also deletes its generated example/translation entries (content/en/api/v2/reference-tables/examples.json, data/api/v2/translate_actions.json), which is a breaking API-doc/SDK regression for users who rely on batch row lookup by primary key. Because the commit is scoped to WAF custom-rule addresses, dropping an unrelated Reference Tables endpoint is likely accidental and should be reverted or split into an explicit, communicated deprecation/removal change.
Useful? React with 👍 / 👎.
1 participant
See DataDog/datadog-api-spec#5267 Test branch datadog-api-spec/test/nicolas.vivet/fix-waf-addresses