Allow on premise bots
By allowing bots which are hosted "on premise" (behind a company firewall), one allow to access systems from that company.
This is the situation for many companies where the infrastructure or services which need to be reachable by bots is not on the public internet.
- A bot is running behind a company firewall
- The bot connects to MS teams, joins a channel, and "listens" to conversations (outbound connection to the internet)
This enables interactions like:
- @bot, list defects (from an in-house issue tracker)
- @bot, add capacity to applicationx (after an authorization phase, on-prem application gets more servers for more capacity)
- [bot]> caution! applicationx experiences a 20% performance hit
We have a solution for this ask and have moved this on our backlog! Keep watching here for updates as we get closer to completing this work.
Any update for this? No comments since July. To me the current model is little bit of a security hole. You have to have public facing interface that can be probed and must be maintained for security issues.
What is blocking this feature ? Is it a possible flood problem or lack of authorization ?
One solution I see for now is to have an authentication layer after publishing the bot, but not the best way obviously. Any communication on this? Is this even being considered?
Yes, please, on-prem bots are really necessary. I'd like to be able to have my bot talk to my jenkins server.
Currently we have applications that use the Slack API in order to listen to channels for commands, kick off application deploys, then respond in channel with the results. The current bot API makes this difficult as we would have to run a URL webservice which reverses our communication path. Rather than have Teams communicate with our URL, I'd like a process on my server to open a connection to Teams.
Brad Van Dorf commented
And allowing the bot to be in group chat in your channels so any of those notifications can go to a whole team of people and everyone can see that someone is working on the issue live where everyone can see how they fix something.
Michael Marks commented
This would be fantastic functionality to have to improve internal operations. As an example, we have an internal dashboard that displays where our traveling employees are on a day to day basis. This requires a lot of manual work and is often wrong because of it. Ideally our developers could create an internal bot that enables people to type something like, "@bot, I am in New York today." which then kicks off some code up update our dashboard with that users location.
Douglas Rockney commented
Note: Cog is looking for people who are interested in a bot for Teams so they can prioritize the work. Vote for the bot on their issue #1194 (https://github.com/operable/cog/issues/1194).
Olivier Jacques commented
Bot can be Hubot, Lita, Cog, ...
Without this, actual "ChatOps" kind of capabilities are not available.