Skip to content

Add slo_query support to datadog_slo_correction#3827

Open
peachprosecutor wants to merge 4 commits into
masterfrom
bvo/slo-correction-slo-query-fresh-provider
Open

Add slo_query support to datadog_slo_correction#3827
peachprosecutor wants to merge 4 commits into
masterfrom
bvo/slo-correction-slo-query-fresh-provider

Conversation

@peachprosecutor
Copy link
Copy Markdown
Contributor

@peachprosecutor peachprosecutor commented May 27, 2026

See API spec PR: https://github.com/DataDog/datadog-api-spec/pull/5816

Updates SLO Correction resource in the datadog provider to support slo_query, which is used for defining global corrections.

slo_query is an optional, nullable field that is used in place of slo_id (which targets a single correction). Because of this, slo_id is no longer required and can be null in response payloads for SLO Corrections defined with slo_query.

@datadog-official
Copy link
Copy Markdown

datadog-official Bot commented May 27, 2026

Pipelines

Fix all issues with BitsAI

⚠️ Warnings

🚦 3 Pipeline jobs failed

Ensure labels | changelog   View in Datadog   GitHub Actions

See error Invalid PR title format. Expected: '[datadog_<resource_or_datasource>] <Description>'.

Run Tests | all-checks   View in Datadog   GitHub Actions

Run Tests | linter-checks   View in Datadog   GitHub Actions

See error Uncommitted changes detected in autogenerated docs. Please run 'make docs' and commit the changes.

Useful? React with 👍 / 👎

This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 449f63f | Docs | Datadog PR Page | Give us feedback!

peachprosecutor and others added 3 commits June 4, 2026 18:15
- Pin datadog-api-client-go to the merged slo_query commit
  (v2.60.1-0.20260604185809-a1941aed2f41) so the provider builds against the
  new SLOCorrection slo_query fields ahead of a tagged client release.
- Add recorded TestAccDatadogSloCorrection_SloQuery cassette (recorded against
  staging, host normalized to api.datadoghq.com); replays green offline.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@peachprosecutor peachprosecutor marked this pull request as ready for review June 4, 2026 22:49
@peachprosecutor peachprosecutor requested review from a team as code owners June 4, 2026 22:49
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