f3nris 4554354e06 fix(sentinelone): accept a skipped UAM update when the alert is already set (1.17.3) ...

The console skips an alert already in the requested state, and 1.17.2
failed every skip: re-assigning an alert to its current holder, as a
second run of the same playbook does, broke the block.

A skipped alert is now read back. Already assigned to that user, or
already carrying that status or verdict, the block succeeds with
already_assigned / already_set; otherwise it fails naming the state the
console holds.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013u8PFdkYuuPiC6JdZBV5x3

2026-09-28 14:48:09 +00:00

..

incident-types

feat(sentinelone): fetch the unified (UAM) alerts (v1.8.0)

2026-09-07 16:16:46 +02:00

mappers

fix(sentinelone): map the unified alert as the console describes it (1.17.0)

2026-09-23 08:28:02 +00:00

scripts

fix(sentinelone): accept a skipped UAM update when the alert is already set (1.17.3)

2026-09-28 14:48:09 +00:00

manifest.yaml

fix(sentinelone): accept a skipped UAM update when the alert is already set (1.17.3)

2026-09-28 14:48:09 +00:00