ConnectionMaster · pull · Jun 30, 2026 · Jun 30, 2026 · Jun 30, 2026 · Jun 30, 2026
diff --git a/.generator/schemas/v2/openapi.yaml b/.generator/schemas/v2/openapi.yaml
@@ -173909,7 +173909,7 @@ paths:
           schema:
             default: true
             type: boolean
-        - description: Filter indicators whose triage state was updated by a specific user UUID.
+        - description: Filter indicators whose triage state was updated by a specific user identified by their handle.
           in: query
           name: worked_by
           required: false

diff --git a/.generator/src/generator/templates/model_generic.j2 b/.generator/src/generator/templates/model_generic.j2
@@ -108,6 +108,21 @@
 {%- endif %}
     end
 
+{%- if model.get("x-keep-typed-in-additional-properties") %}
+
+    # Builds the object from hash, also mirroring typed fields into additional_properties.
+    # @param attributes [Hash] Model attributes in the form of hash
+    # @return [Object] Returns the model itself
+    # @!visibility private
+    def build_from_hash(attributes)
+      super
+      self.class.attribute_map.each_pair do |attr, json_key|
+        self.additional_properties[json_key] = self.send(attr) if attributes.key?(json_key)
+      end
+      self
+    end
+{%- endif %}
+
 {%- set ns = namespace(hasValidation=False) %}
 {%- for attr, definition in model.get("properties", {}).items() %}
       {%- set required = attr in model.get("required", []) %}

diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -1,5 +1,40 @@
 # CHANGELOG
 
+## 2.56.0/2026-06-30
+
+### Added
+* Add the uk1 data center. [#3530](https://github.com/DataDog/datadog-api-client-ruby/pull/3530)
+* [obs-pipelines] Add TLS support to cloud_prem destination [#3525](https://github.com/DataDog/datadog-api-client-ruby/pull/3525)
+* Add OpenAPI spec for k9-integration-api security findings and vulnerabilities [#3522](https://github.com/DataDog/datadog-api-client-ruby/pull/3522)
+* Document metrics volume includes [#3520](https://github.com/DataDog/datadog-api-client-ruby/pull/3520)
+* Add buffer configuration to ClickHouse destination [#3519](https://github.com/DataDog/datadog-api-client-ruby/pull/3519)
+* Add public API endpoints for feature flag variant create, update, and delete [#3517](https://github.com/DataDog/datadog-api-client-ruby/pull/3517)
+* Add public v2 OpenAPI operations for governance controls [#3515](https://github.com/DataDog/datadog-api-client-ruby/pull/3515)
+* Add ObservabilityPipelineClickhouseDestination to OpenAPI spec [#3514](https://github.com/DataDog/datadog-api-client-ruby/pull/3514)
+* Add ObservabilityPipelineWebsocketSource to schema [#3512](https://github.com/DataDog/datadog-api-client-ruby/pull/3512)
+* Add security_filters and rules resource types to terraform export endpoints [#3510](https://github.com/DataDog/datadog-api-client-ruby/pull/3510)
+* Add OpenAPI for Cloud Cost Management custom forecast endpoints [#3509](https://github.com/DataDog/datadog-api-client-ruby/pull/3509)
+* Add Edit and Delete Notice Update and Slack icon support in API spec [#3504](https://github.com/DataDog/datadog-api-client-ruby/pull/3504)
+* Add OpenAPI spec for RUM Remote Config endpoints [#3499](https://github.com/DataDog/datadog-api-client-ruby/pull/3499)
+* Add OpenAPI spec for code-coverage PR summary and files endpoints [#3498](https://github.com/DataDog/datadog-api-client-ruby/pull/3498)
+* feat(test-optimization): update service settings API with override and inherit fields [#3497](https://github.com/DataDog/datadog-api-client-ruby/pull/3497)
+* Add public API for security findings automation rules [#3495](https://github.com/DataDog/datadog-api-client-ruby/pull/3495)
+* Add OpenAPI spec for governance insights [#3490](https://github.com/DataDog/datadog-api-client-ruby/pull/3490)
+* Add OpenAPI specs for reporting schedule endpoints [#3484](https://github.com/DataDog/datadog-api-client-ruby/pull/3484)
+* Add LogsArrayMapProcessor to OpenAPI v1 spec [#3458](https://github.com/DataDog/datadog-api-client-ruby/pull/3458)
+* Update GetBudget API spec with cost query parameters and custom forecast fields [#3457](https://github.com/DataDog/datadog-api-client-ruby/pull/3457)
+
+### Changed
+* Update worked_by param to accept handle instead of UUID [#3529](https://github.com/DataDog/datadog-api-client-ruby/pull/3529)
+* Add support for running CI jobs [#3516](https://github.com/DataDog/datadog-api-client-ruby/pull/3516)
+* Mark tag indexing rule endpoints as Preview in API spec [#3496](https://github.com/DataDog/datadog-api-client-ruby/pull/3496)
+
+### Deprecated
+* Remove Compliance Findings rule-based view endpoint from OpenAPI v2 [#3526](https://github.com/DataDog/datadog-api-client-ruby/pull/3526)
+
+### Fixed
+* Fix test by adding on_missing_data options to the req payload [#3524](https://github.com/DataDog/datadog-api-client-ruby/pull/3524)
+
 ## 2.55.0/2026-06-17
 
 ### Added

diff --git a/features/v1/security_monitoring.feature b/features/v1/security_monitoring.feature
@@ -9,23 +9,23 @@ Feature: Security Monitoring
     And a valid "appKeyAuth" key in the system
     And an instance of "SecurityMonitoring" API
 
-  @generated @skip @team:DataDog/k9-cloud-siem
+  @generated @skip @team:DataDog/cloud-siem
   Scenario: Add a security signal to an incident returns "Bad Request" response
     Given new "AddSecurityMonitoringSignalToIncident" request
     And request contains "signal_id" parameter from "REPLACE.ME"
     And body with value {"incident_id": 2066, "version": 0}
     When the request is sent
     Then the response status is 400 Bad Request
 
-  @generated @skip @team:DataDog/k9-cloud-siem
+  @generated @skip @team:DataDog/cloud-siem
   Scenario: Add a security signal to an incident returns "Not Found" response
     Given new "AddSecurityMonitoringSignalToIncident" request
     And request contains "signal_id" parameter from "REPLACE.ME"
     And body with value {"incident_id": 2066, "version": 0}
     When the request is sent
     Then the response status is 404 Not Found
 
-  @replay-only @team:DataDog/k9-cloud-siem
+  @replay-only @team:DataDog/cloud-siem
   Scenario: Add a security signal to an incident returns "OK" response
     Given new "AddSecurityMonitoringSignalToIncident" request
     And request contains "signal_id" parameter with value "AQAAAYDiB_Ol8PbzFAAAAABBWURpQl9PbEFBQU0yeXhGTG9ZV2JnQUE"
@@ -34,23 +34,23 @@ Feature: Security Monitoring
     Then the response status is 200 OK
     And the response "status" is equal to "done"
 
-  @generated @skip @team:DataDog/k9-cloud-siem
+  @generated @skip @team:DataDog/cloud-siem
   Scenario: Change the triage state of a security signal returns "Bad Request" response
     Given new "EditSecurityMonitoringSignalState" request
     And request contains "signal_id" parameter from "REPLACE.ME"
     And body with value {"archiveReason": "none", "state": "open", "version": 0}
     When the request is sent
     Then the response status is 400 Bad Request
 
-  @generated @skip @team:DataDog/k9-cloud-siem
+  @generated @skip @team:DataDog/cloud-siem
   Scenario: Change the triage state of a security signal returns "Not Found" response
     Given new "EditSecurityMonitoringSignalState" request
     And request contains "signal_id" parameter from "REPLACE.ME"
     And body with value {"archiveReason": "none", "state": "open", "version": 0}
     When the request is sent
     Then the response status is 404 Not Found
 
-  @replay-only @team:DataDog/k9-cloud-siem
+  @replay-only @team:DataDog/cloud-siem
   Scenario: Change the triage state of a security signal returns "OK" response
     Given new "EditSecurityMonitoringSignalState" request
     And request contains "signal_id" parameter with value "AQAAAYDiB_Ol8PbzFAAAAABBWURpQl9PbEFBQU0yeXhGTG9ZV2JnQUE"
@@ -59,23 +59,23 @@ Feature: Security Monitoring
     Then the response status is 200 OK
     And the response "status" is equal to "done"
 
-  @generated @skip @team:DataDog/k9-cloud-siem
+  @generated @skip @team:DataDog/cloud-siem
   Scenario: Modify the triage assignee of a security signal returns "Bad Request" response
     Given new "EditSecurityMonitoringSignalAssignee" request
     And request contains "signal_id" parameter from "REPLACE.ME"
     And body with value {"assignee": "773b045d-ccf8-4808-bd3b-955ef6a8c940", "version": 0}
     When the request is sent
     Then the response status is 400 Bad Request
 
-  @generated @skip @team:DataDog/k9-cloud-siem
+  @generated @skip @team:DataDog/cloud-siem
   Scenario: Modify the triage assignee of a security signal returns "Not Found" response
     Given new "EditSecurityMonitoringSignalAssignee" request
     And request contains "signal_id" parameter from "REPLACE.ME"
     And body with value {"assignee": "773b045d-ccf8-4808-bd3b-955ef6a8c940", "version": 0}
     When the request is sent
     Then the response status is 404 Not Found
 
-  @replay-only @team:DataDog/k9-cloud-siem
+  @replay-only @team:DataDog/cloud-siem
   Scenario: Modify the triage assignee of a security signal returns "OK" response
     Given new "EditSecurityMonitoringSignalAssignee" request
     And request contains "signal_id" parameter with value "AQAAAYDiB_Ol8PbzFAAAAABBWURpQl9PbEFBQU0yeXhGTG9ZV2JnQUE"