Skip to content

fix(pipedv1): use FindSlackGroups for group mentions in trigger-failed notification#6981

Open
Ahmad-Faraj wants to merge 1 commit into
pipe-cd:masterfrom
Ahmad-Faraj:fix/trigger-failed-group-mentions
Open

fix(pipedv1): use FindSlackGroups for group mentions in trigger-failed notification#6981
Ahmad-Faraj wants to merge 1 commit into
pipe-cd:masterfrom
Ahmad-Faraj:fix/trigger-failed-group-mentions

Conversation

@Ahmad-Faraj

Copy link
Copy Markdown

What this PR does:

The failed-trigger notification in pipedv1 fills the group mentions by calling FindSlackUsers, so configured Slack groups are never mentioned when a trigger fails. Looks like a copy-paste from the line above. The v0 piped has it right. This switches it to FindSlackGroups.

Which issue(s) this PR fixes:

None

Does this PR introduce a user-facing change?:

  • How are users affected by this change: Slack group mentions now work for trigger-failed notifications in pipedv1.
  • Is this breaking change: no
  • How to migrate (if breaking change): n/a

…d notification

notifyDeploymentTriggerFailed assigns the groups list from FindSlackUsers,
so configured Slack groups are never mentioned on trigger failure. The
v0 piped counterpart uses FindSlackGroups here.

Signed-off-by: Ahmad Faraj <ahmedfrag4040@gmail.com>

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Fixes pipedv1 failed-trigger Slack notifications so configured Slack groups are mentioned correctly (matching the behavior already used for “deployment triggered” notifications and aligning with v0 piped behavior described in the PR).

Changes:

  • Replace an incorrect FindSlackUsers(...) call with FindSlackGroups(...) when populating MentionedGroups for EVENT_DEPLOYMENT_TRIGGER_FAILED.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants