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
In summary, any ongoing mirrors using bridge_with_slack on a classic Slack app should continue to work. However, users won't be able to create new mirrors once the class Slack app has been discontinued because it uses RTM API. It is highly recommended by Slack to migrate to Socket Mode API.
One recommended fix that seems to be the easiest is to just migrate to rtm.connect. However, RTM API itself must be configured using a classic Slack app. This means after June 4 2024, new Slack users won't be able to use our bridge_with_slack even when we've migrated to rtm.connect from rtm.start.
On the other hand, migrating to the recommended Socket Mode would likely require overhauling most of bridge_with_slack.py. However, this approach is more future-proof and allows the possibility to expand bridge_with_slack with more features provided by the Socket Mode API and other features down the line.
Documentation
Right now it's still pointing the user to create the classic Slack app.
The text was updated successfully, but these errors were encountered:
PieterCK
changed the title
Slack Bridge: Changes from modern Slack App
Slack Bridge: Discontinuation of classic Slack App
May 13, 2024
Thanks for your interest in Zulip! You have attempted to claim an issue without the label "help wanted". You can only claim and submit pull requests for issues with the help wanted label.
If this is your first time here, we recommend reading our guide for new contributors before getting started.
Welcome to Zulip, @PieterCK! We just sent you an invite to collaborate on this repository at https://github.com/zulip/python-zulip-api/invitations. Please accept this invite in order to claim this issue and begin a fun, rewarding experience contributing to Zulip!
Here's some tips to get you off to a good start:
Join me on the Zulip developers' server, to get help, chat about this issue, and meet the other developers.
As you work on this issue, you'll also want to refer to the Zulip code contribution guide, as well as the rest of the developer documentation on that site.
See you on the other side (that is, the pull request side)!
Currently we use the Slacks legacy RTM API as the
"listener" from Slack to Zulip. This commit replaces
RTM API for the supported Events API instead.
Fixeszulip#825.
馃搫 Overview
Slack is discontinuing its classic Slack app. On June 4 2024, user won't be able to create the classic Slack app anymore.
This issue will highlight how this change will impact our "real-time slack mirror" feature, specifically
bridge_with_slack.py
and any relevant files.Relevant links:
Discontinuing new creation of Classic Slack apps and legacy custom integration bot users
Slack Migration Guide
CZO discussion: here.
In summary, any ongoing mirrors using
bridge_with_slack
on a classic Slack app should continue to work. However, users won't be able to create new mirrors once the class Slack app has been discontinued because it uses RTM API. It is highly recommended by Slack to migrate to Socket Mode API.see list of available API: slack_sdk
bridge_with_slack.py
One recommended fix that seems to be the easiest is to just migrate to
rtm.connect
. However, RTM API itself must be configured using a classic Slack app. This means after June 4 2024, new Slack users won't be able to use ourbridge_with_slack
even when we've migrated tortm.connect
fromrtm.start
.On the other hand, migrating to the recommended Socket Mode would likely require overhauling most of
bridge_with_slack.py
. However, this approach is more future-proof and allows the possibility to expandbridge_with_slack
with more features provided by the Socket Mode API and other features down the line.Documentation
The text was updated successfully, but these errors were encountered: