argoproj/argo-events

Expand Slack Trigger Capabilities

Open

#1,301 opened on Aug 9, 2021

View on GitHub
 (10 comments) (37 reactions) (1 assignee)Go (829 forks)auto 404
enhancementhelp wanted

Repository metrics

Stars
 (2,679 stars)
PR merge metrics
 (PR metrics pending)

Description

Is your feature request related to a problem? Please describe. We'd like to be able to support a variety of Slack features when sending notifications/events to Slack:

Describe the solution you'd like Expand the Spec to cover more of the chat.postMessage API from slack, so that we can use those features.

Describe alternatives you've considered Creating a custom trigger for these use-cases, but the API is standard in Slack, so this functionality should be straightforward to add to the main code.

Additional context

Message from the maintainers:

If you wish to see this enhancement implemented please add a 👍 reaction to this issue! We often sort issues this way to know what to prioritize.

Contributor guide

Research direction
Examine the existing Slack trigger implementation in pkg/events/... and the corresponding spec definitions. Study the Slack chat.postMessage API for block kit, attachments, and threading. Implement new fields in the trigger spec and update the event handler to support them.
Tech stack
go
Domain
backend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitGoKubernetes basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70