Skip to content

Add API spec for severity modifiers automation pipelines - #3641

Open
api-clients-generation-pipeline[bot] wants to merge 1 commit into
masterfrom
datadog-api-spec/generated/6306
Open

Add API spec for severity modifiers automation pipelines#3641
api-clients-generation-pipeline[bot] wants to merge 1 commit into
masterfrom
datadog-api-spec/generated/6306

Conversation

@api-clients-generation-pipeline

Copy link
Copy Markdown
Contributor

@datadog-datadog-prod-us1-2

datadog-datadog-prod-us1-2 Bot commented Aug 3, 2026

Copy link
Copy Markdown

Pipelines  Tests

Unblock PR with BitsAI

⚠️ Warnings

🚦 1 Pipeline job failed

Run Tests | test / test (3.2, ubuntu-latest)   View in Datadog   GitHub Actions

🔧 Fix in code. This looks caused by changes in this PR. ArgumentError: invalid value for "action", action cannot be nil at ./lib/datadog_api_client/v2/models/severity_modifier_rule_attributes_response.rb:155.
📋 Copy prompt for your agent
CI on my pull request is failing. Help me find and fix the root cause of each failing job below — they were flagged as caused by changes in this PR, so focus on the diff. For each job, explain the failure and propose a fix.

Branch: datadog-api-spec/generated/6306

Run Tests | test / test (3.2, ubuntu-latest)
Commit: eaac17829d60e75e6db629bb1329daa0b17fa76c
Error (code / test):
ArgumentError: invalid value for "action", action cannot be nil at ./lib/datadog_api_client/v2/models/severity_modifier_rule_attributes_response.rb:155.
CI job: https://github.com/DataDog/datadog-api-client-ruby/actions/runs/30802048037/job/91648633213

🧪 4 Tests failed in 1 job

Run Tests | test   GitHub Actions

Delete a severity modifier rule returns "Rule successfully deleted." response from Security Monitoring at features/v2/security_monitoring.feature   View in Datadog
There are unused HTTP interactions left in the cassette:
  - [delete https://api.datadoghq.com/api/v2/security/findings/automation/severity_modifier_rules/ec796c54-ec53-4b2f-bb14-36d4b224f92c] => [204 ""]
  - [delete https://api.datadoghq.com/api/v2/security/findings/automation/severity_modifier_rules/ec796c54-ec53-4b2f-bb14-36d4b224f92c] => [404 "{\"errors\":[{\"status\":\"404\",\"title\":\"Not Found\",\"detail\":\"rule does not exist\"}]}"]
Get a severity modifier rule returns "Successfully retrieved the severity modifier rule" response from Security Monitoring at features/v2/security_monitoring.feature   View in Datadog
There are unused HTTP interactions left in the cassette:
  - [get https://api.datadoghq.com/api/v2/security/findings/automation/severity_modifier_rules/fec045ba-40ba-42ef-a107-f7fba8717e11] => [200 "{\"data\":{\"id\":\"fec045ba-40ba-42ef-a107-f7fba8717e11\",\"type\":\"severity_modifier_r"]
  - [delete https://api.datadoghq.com/api/v2/security/findings/automation/severity_modifier_rules/fec045ba-40ba-42ef-a107-f7fba8717e11] => [204 ""]

View all failed tests

ℹ️ Info

No other issues found (see more)

❄️ No new flaky tests detected

Useful? React with 👍 / 👎

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

@api-clients-generation-pipeline
api-clients-generation-pipeline Bot force-pushed the datadog-api-spec/generated/6306 branch from 49f8a60 to 2a61417 Compare August 3, 2026 09:35

@BusyBeaver-42 BusyBeaver-42 left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

No changes unrelated to severity modifiers.

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