feat(rum): add rum_teams_ownership_mappings resource

[michael-richey]

Summary

RUM teams-ownership mappings — no PATCH endpoint, so update is implemented as delete-then-recreate.

Stacked on #721 (rum_replay_playlists).

Design

• attributes.application_id is a RUM application uuid → remapped via resource_connections (rum_applications).
• attributes.team_handle is a stable handle (teams are mapped by name:handle and the handle is preserved across orgs), so it is not remapped. The dependency on teams is soft (documented in README) rather than a resource_connection, which would mis-remap a handle as a uuid.
• Create data has no id (server-assigned, popped); update = delete old destination mapping + POST new.
• excluded_attributes: id + server-managed created_at/created_by/org_id.

Changes

• datadog_sync/model/rum_teams_ownership_mappings.py (new)
• datadog_sync/models/__init__.py — register
• tests/unit/test_rum_teams_ownership_mappings.py (new) — 7 unit tests
• README.md — add rum_teams_ownership_mappings (depends on rum_applications, teams)

Testing

• pytest tests/unit/test_rum_teams_ownership_mappings.py → 7 passed
• Full unit suite: no new failures.

Follow-up

Integration tests + VCR cassettes deferred (require sandbox-org API access).

[michael-richey]

Nice work on this resource.

The delete-then-recreate update strategy is well documented and correctly tested, and I agree with treating team_handle as stable/non-remapped while remapping only application_id.

No blocking issues found in this PR diff.

[Copilot]

Copilot review overview

🟡 Changes recommended

The update path can become unrecoverable after deletion succeeds but recreation fails.

Get a fresh assessment by requesting another Copilot review.

Review effort: Balanced
Findings: 1

Open (1)

• Use state-aware delete wrapper to prevent stale destination IDs · New

What changed in this PR

Adds synchronization support for RUM team ownership mappings, including application ID remapping and delete/recreate updates.

Changes:

• Adds and registers the new resource model.
• Documents dependencies and supported-resource status.
• Adds unit coverage for CRUD and connection behavior.

File	Description
datadog_sync/​model/​rum_teams_ownership_mappings.py	Implements synchronization behavior.
datadog_sync/​models/​__init__.py	Registers the resource model.
tests/​unit/​test_rum_teams_ownership_mappings.py	Tests model operations and ID remapping.
README.md	Documents support and dependencies.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[michael-richey]

Fixed in 6a6c2621. update_resource now uses _delete_resource (the state-aware wrapper from BaseResource) instead of calling delete_resource directly. If DELETE succeeds but POST fails, the state entry is removed after the successful delete, so the next retry recovers via the create path instead of DELETEing a stale ID that 404s forever. New test verifies state is cleaned up when DELETE succeeds but POST fails.

[michael-richey]

Good implementation for this API shape.

What I liked:

• PATCH-only endpoint behavior is handled via create_or_update_resource.
• Clear normalization of ids from <application_id>:<id> back to API id in import path.
• Delete+recreate strategy for app-id changes is explicit and practical.

No blocking issues from my side.