Adding Beep Boop multi-team support and fixing a few error cases #4
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I added the ability to run this bot as a multi-team bot on Beep Boop by wiring in the
beepboop-botkit
module. As a multi-team bot it allows you to make it public and easy for anyone to add directly to their team via an "Add to Slack" button. More details on what's happening with thebeepboop-botkit
module can be found here, but in essence, instead of expecting aSLACK_TOKEN
when the bot starts up, it receives messages over a socket connection to a Beep Boop service when teams add/remove the bot. This allows your single bot process to handle many teams, and also allows Beep Boop to scale your bot to multiple processes if needed.I left in the ability to run in single team mode as that's sometimes useful for development, or in case others that fork this want that functionality.