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
This is a noop, but will ensure that the old RTM bot can co-exist in the same database as the newer version of the app with granular scopes.
Upgrade to slack-ruby-bot-server-rtm , which extracts real-time components, e.g. slack-ruby/slack-shellbot@db40cb5. This gem was split out from slack-ruby-bot-server.
Deploy the new app. Now there are two versions of the app running on top of the same database, one is the legacy and the other is the granular scopes app. Both work.
Switch DNS, new bot registrations use the new granular scopes app. Make sure in Slack the event URLs are configured properly to point to this DNS.
Existing teams can re-install with new granular scopes, the old bot will stop working and the new one will take over.
The text was updated successfully, but these errors were encountered:
Long version: https://code.dblock.org/2020/11/30/migrating-classic-slack-ruby-bots-to-granular-permissions.html
Phase 1
This is a noop, but will ensure that the old RTM bot can co-exist in the same database as the newer version of the app with granular scopes.
oauth_version
andoauth_scope
, e.g. slack-ruby/slack-shellbot@bda862c. See https://github.com/slack-ruby/slack-ruby-bot-server/blob/master/UPGRADING.md#upgrading-to--120.Make sure everything is working, keep v1 of the bot running in its own container/app.
Phase 2
The text was updated successfully, but these errors were encountered: