Skip to content
This repository has been archived by the owner on Mar 29, 2023. It is now read-only.

[FEAT] Ability to configure slack message channel routing #154

Closed
DanHatesNumbers opened this issue Jan 10, 2020 · 1 comment
Closed

[FEAT] Ability to configure slack message channel routing #154

DanHatesNumbers opened this issue Jan 10, 2020 · 1 comment
Labels
enhancement New feature or request slack-connector wontfix This will not be worked on

Comments

@DanHatesNumbers
Copy link
Contributor

Is your feature request related to a problem? Please describe.
As a Kiln user
I want to be able to send Slack notifications to specific channels based on the application they relate to
So that I can see the specific information I'm interested in

Describe the solution you'd like
Some way of configuring a mapping of application names to slack channel IDs.

Additional context
Add any other context or screenshots about the feature request here.

@DanHatesNumbers
Copy link
Contributor Author

One option would be to have the CLI include the configured Slack channel from kiln.toml in the ToolReport payload, have the Data-collector publish this information to another Kafka topic if the run if from CI (To prevent data races with local modifications), then have the Slack connector maintain a list of triples for project-branch-channel. The kafka topic could use the first two elements as the message key and use topic compaction to speed up startup.

This approach avoids coupling the Slack connector config to the tool report structure and having to also couple it to the Dependency Events or any other finding events.

@DM-sb DM-sb added the wontfix This will not be worked on label Mar 29, 2023
@DM-sb DM-sb closed this as completed Mar 29, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request slack-connector wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

2 participants