Repository navigation
feat(automation): support war room triggered Automations - #237
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add war room trigger support to the curated
automationcommands, wrapping the API fields from go-flashduty v0.15.20:automation creategains--war-room-trigger,--war-room-channel-ids, and--war-room-severities. A war-room-only rule sends a placeholder cron with the schedule trigger disabled, same as an HTTP POST-only rule. The trigger requires both filter lists, enforced client-side.automation updategains--enable-war-room-trigger,--disable-war-room-trigger, and filter replacement flags.automation runsacceptswar_room_createdfor--trigger-kind.When an AI SRE war room (IM group chat) is created for a matching incident, the agent runs inside that group chat with
trigger_kind=war_room_created.