Turn on/off various different types of integration
dblock opened this issue · comments
Newer bots can be entirely event based, without any real-time components. Need a feature in slack-ruby-bot-server to make RTM optional (possibly by doing slack-ruby/slack-ruby-bot-server#124) and explain here how to turn on/off various types of integrations.
Got you.
And I'm still waiting the new release of slack-ruby for the slack api v2.
We are still stuck on the legacy version.
I remember someone was already working on it...
Are we close to the new release or something else?
Do you mean switching slack-ruby-bot-server to use oauth v2? I am certainly not working on it and don't think anyone is. The API is available in the client since slack-ruby/slack-ruby-client#303.
There was slack-ruby/slack-ruby-bot-server#125 but it was left unfinished, please feel free to pick it up!
Yeah, I was just pointing that.
Simply put, I think we need to make using v2 as default mode.
Let me comeback and pick it up sooner.
I am pretty much done with slack-ruby/slack-ruby-bot-server#129 which removes the real-time portion of slack-ruby-bot-server. For apps that don't need it, one just needs to set the oauth scopes like this:
SlackRubyBotServer.configure do |config|
config.oauth_scope = ['channels:read', 'chat:write:user']
endThat should be it, and slack-ruby-bot-server-events works out of the box.
I recommend updating this tutorial and removing the RTM part altogether.
Gotcha!
That should be it, and slack-ruby-bot-server-events works out of the box.
Did you confirmed it with the new version of slack app?
That should be it, and slack-ruby-bot-server-events works out of the box.
Did you confirmed it with the new version of slack app?
I didn't, so you get the v2 auth problem. I'll look into it.