docs: Add brief migration guide#260
Conversation
wasabigeek
force-pushed
the
add-migration-docs
branch
from
a61f8c4 to
9b37a82
Compare
wasabigeek
force-pushed
the
add-migration-docs
branch
from
9b37a82 to
73ceea5
Compare
|
|
||
| ## Migrating to slack-ruby-bot-server | ||
| Overview: | ||
| - Create a new Slack App as [advised by Slack](https://api.slack.com/legacy/custom-integrations/legacy-tokens#migrating-from-legacy). |
There was a problem hiding this comment.
This is confusing. I think we should tell users to go through the tutorial/setup of slack-ruby-bot-server as in that doc, then copy command classes, then do the workflow that you suggest. And explain what happens when you do that and the fact that other teams can install the bot too then, which may not be what you want (and needs to be prevented).
There was a problem hiding this comment.
I am actually a little confused by Slack itself. If I understood correctly, slack-ruby-bot-server requires the latest Slack Apps, but there are also legacy tokens AND class Slack Apps, both with subtly different migration strategies on the Slack end. Did I get that right, and should I gloss over this?
There was a problem hiding this comment.
Ok! Any more comments?
|
I merged this, thank you. |
2 participants
Fixes #252.
I may not have the opportunity to verify this flow for some time, if anyone has tried it, do let me know if it works / there are any issues!