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

Browse Source

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

...

This commit is contained in:

Guillaume Bourgeois

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

parent 71f8cd970e

commit 4554354e06

4 changed files with 43 additions and 7 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download Patch File Download Diff File Expand all files Collapse all files

integrations/sentinelone/manifest.yaml

+2 -2

File diff suppressed because one or more lines are too long