Skip to content

Remove duplicate MonitorFormulaAndFunctionCostDataSource schema#35296

Open
api-clients-generation-pipeline[bot] wants to merge 1 commit intomasterfrom
datadog-api-spec/generated/5265
Open

Remove duplicate MonitorFormulaAndFunctionCostDataSource schema#35296
api-clients-generation-pipeline[bot] wants to merge 1 commit intomasterfrom
datadog-api-spec/generated/5265

Conversation

@api-clients-generation-pipeline
Copy link
Contributor

Copy link

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

https://github.com/DataDog/documentation/blob/f817459d0eed9c388680d21986b343b1e6710a75/data/api/v2/full_spec.yaml#L97089-L97090
P1 Badge Restore BatchRowsQuery operation in v2 API spec

This change removes the entire /api/v2/reference-tables/queries/batch-rows operation from data/api/v2/full_spec.yaml (and matching entries in config/_default/menus/api.en.yaml and data/api/v2/translate_actions.json), which makes the batch row lookup API disappear from published docs and generated operation metadata. Because this commit is scoped to deduplicating monitor data-source schemas, dropping an unrelated Reference Tables endpoint is a breaking regression for users that depend on batch row queries by primary key.

ℹ️ 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".

@api-clients-generation-pipeline api-clients-generation-pipeline bot force-pushed the datadog-api-spec/generated/5265 branch from f817459 to 7e2064d Compare March 17, 2026 12:51
@github-actions github-actions bot removed the Architecture Everything related to the Doc backend label Mar 17, 2026
@api-clients-generation-pipeline api-clients-generation-pipeline bot force-pushed the datadog-api-spec/generated/5265 branch from 7e2064d to 8de476c Compare March 17, 2026 13:28
Copy link

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 8de476c3eb

ℹ️ 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".

- server.request.path_params
- server.request.query
- server.request.headers
- server.request.headers.no_cookies

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Restore removed custom-rule input addresses in AppSec enum

This change drops multiple previously documented ApplicationSecurityWafCustomRuleConditionInputAddress enum values (for example server.request.headers, server.request.custom-auth, server.response.body, and server.llm.event), which means OpenAPI-based validation and generated SDKs will now reject existing custom-rule payloads that use those addresses even though this commit is scoped to monitor schema deduplication. In practice, users updating clients/spec tooling from this file can no longer represent rules that were valid before.

Useful? React with 👍 / 👎.

@api-clients-generation-pipeline api-clients-generation-pipeline bot force-pushed the datadog-api-spec/generated/5265 branch from 8de476c to 86ccbc4 Compare March 17, 2026 14: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