You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Unfortunately, we cannot support all the solutions because of the too big maintenance efforts. However, what we can do, is to abstract the communication platforms and make them extensible – just how we did with executors and sources.
Acceptance Criteria
Extract current communication platforms to plugins
Define gRPC API contract
Update configuration (communications property)
Release the comm platforms as separate plugins
Ensure the plugins are properly downloaded during Botkube startup
Create botkube-plugins-contrib repo (or similar), to host community-maintained comm platform plugins
Extract some of the current platforms to the botkube-plugins-contrib - e.g. elasticsearch, Teams?
Migrate some of the comm platform related issues to the botkube-plugins-contrib repo
Make sure documentation is up-to-date, create one if needed
Add test coverage for happy-path (unit or e2e test)
Record raw demo video for the user-facing changes
Reason
Ensure users can use Botkube with their own communication platforms, even though we can't support them officially.
The text was updated successfully, but these errors were encountered:
Overview
Currently, there are multiple feature requests for different chat platforms:
Unfortunately, we cannot support all the solutions because of the too big maintenance efforts. However, what we can do, is to abstract the communication platforms and make them extensible – just how we did with executors and sources.
Acceptance Criteria
communications
property)botkube-plugins-contrib
repo (or similar), to host community-maintained comm platform pluginsbotkube-plugins-contrib
- e.g. elasticsearch, Teams?botkube-plugins-contrib
repoReason
Ensure users can use Botkube with their own communication platforms, even though we can't support them officially.
The text was updated successfully, but these errors were encountered: