-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create sources-slack component #3945
Comments
Hi, I followed the process given in contributing to airy, for How to run the whatsapp/connector image locally within a local airy-core instance inside minikube's registry? |
The
sources-slack
component will interact with Slack API in order to send and receive messages and/or other events. This component should have one running workload (deployment), for retrieving and sending the messages to/from Slack calledsources-slack-connector
. For a quick explanation on airy sources architecture is neededMessages (events) coming from slack
Replies send to slack
Example of a similar component
If you have a look to sources-whatsapp component you will find the application of the concepts above.
CI rules
For pushing the docker images, the Bazel ruleset must be included in the component
Helm charts
The component is packaged into its own Helm chart, that will be pushed with Bazel to https://helm.airy.co. The Helm templates should be added to the
helm
directory of the component and the Bazel rules should be inhelm/BUILD
.Slack API
Few links to the Slack documentation for the the integration.
For any question please don't hesitate to reply to this issue. Good luck 💪
The text was updated successfully, but these errors were encountered: