Pulumi Cloud Stack Alert Rule Suppression Windows and Deduplication

Pulumi Cloud alert rules can notify owners when a stack update fails or drift is detected, but repeated failed pulumi up runs can generate duplicate notifications across email, Slack, PagerDuty, or webhook channels.

The goal is to retain failure and drift alerts while suppressing repeated notifications for the same unresolved stack issue during an active incident.

It is unclear whether Pulumi Cloud provides native alert suppression windows, snooze durations, or deduplication for recurring stack events, and whether these options differ between free and paid organization tiers. Alert rule creation may also depend on organization admin or stack-specific RBAC permissions.

Does Pulumi Cloud support alert suppression windows or deduplication for repeated stack failures? Which organization role or stack permission is required to create and edit alert rules? Are suppression or snooze settings available on all Pulumi Cloud pricing tiers?