Create sources-slack component

[juan-sebastian]

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 called sources-slack-connector. For a quick explanation on airy sources architecture is needed

Messages (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 in helm/BUILD.

Slack API

Few links to the Slack documentation for the the integration.

• https://api.slack.com/messaging/retrieving
• https://api.slack.com/messaging/sending
• https://api.slack.com/messaging/webhooks

For any question please don't hesitate to reply to this issue. Good luck 💪

[ParthFogteams]

Hi,
I am trying to run the sources-whatsapp connector in a local instance of airy-core inside Minikube; just to understand it better, so as to go on to further build a sources-slack component.

I followed the process given in contributing to airy, for //backend/components/whatsapp/connector:image but the kubectl patch command given to run image on airy-core leads to a failure state in the container and the api-communication pod shows a crashloopbackoff status.

How to run the whatsapp/connector image locally within a local airy-core instance inside minikube's registry?