Driftwatch

Datadog / Datadog API v2 /

Breaking

/api/v2/csm/ownership/{resource_id}/{owner_type}/feedback moved to /api/v2/security/ownership/{resource_id}/{owner_type}/feedback

What changed

The same operations are now documented at a new path. Requests to the old one may 404, so update the URL; anything else that changed at the new path is listed separately.

Affects /api/v2/csm/ownership/{resource_id}/{owner_type}/feedback.

/api/v2/csm/ownership/{resource_id}/{owner_type}/feedback → /api/v2/security/ownership/{resource_id}/{owner_type}/feedback

Who is affected

Code that calls /api/v2/csm/ownership/{resource_id}/{owner_type}/feedback.

Before and after

WhereBeforeAfter
/api/v2/csm/ownership/{resource_id}/{owner_type}/feedback/api/v2/csm/ownership/{resource_id}/{owner_type}/feedback/api/v2/security/ownership/{resource_id}/{owner_type}/feedback

Code that breaks

// Was:
await client.request("/api/v2/csm/ownership/{resource_id}/{owner_type}/feedback");
// Now:
await client.request("/api/v2/security/ownership/{resource_id}/{owner_type}/feedback");

Based on Datadog’s published API specification. How severity is decided.