How to handle muliple hubots on the same ST2 instance

A question following AHH#11.

How should ST2 handle multiple instances of hubot? Our ST2 installation has two hubots attached (both using the same chatops user), our own hubot that pre-dates us installing ST2 and the docker container version. If we run a chatops.post_message to a user, they receive an message from both bots as a DM (in slack) and I would expect if both bots were in the same channel the messages would be duplicated. However if your talking to a single Bot as a DM the messages are routed correctly.

The question is how to handle this? I think one option is to only have a single bot, but it would be nice to attache aliases to different bots (e.g. lab, dev & prod) that act on different environments via the same ST2 instance.

[cognifloyd]

TL;DR; Yes. I think we can close this.

As the implementation for multi-bot routing will depend on which bot backend is used, I think we can close this for hubot as hubot itself is on the way out.

Err-stackstorm already has this feature (thanks @nzlosh!). afaik, that uses the routing keys that ST2 core already makes available. Unlike Errbot, our Hubot integration only used the routing key to distinguish between chat providers (slack, irc, etc), not individual bots.

Once we replace Hubot with OpsDroid (no integration exists yet), OpsDroid also supports naming each chat service connection, so it should be able to use the route key flexibly like err-stackstorm does.

[jjm]

@StackStorm/maintainers @StackStorm/contributors Should we close this one off? I raised it around 5 years ago and there’s ongoing discussions on the future of hubot.

Just reviewing and cleaning up my still open raised issues.