Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] ping message isn't filtered by Channel Id (mattermost) #205

Closed
daegeun-ha opened this issue Oct 18, 2019 · 2 comments
Labels
bug

Comments

@daegeun-ha
Copy link

@daegeun-ha daegeun-ha commented Oct 18, 2019

Describe the bug
ping message isn't filtered by channel id.

To Reproduce
Steps to reproduce the behavior:

  1. Make two different channels in same mattermost team.
  2. Figure one channel to botkube pod. (botkube pod only knows one channel)
  3. Send 'ping' message from two different channels.
  4. You can see 'pong' message in both channels!

Expected behavior
Only one figured pod that is figured in botkube pod can receive 'pong' message

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context

@PrasadG193

This comment has been minimized.

Copy link
Member

@PrasadG193 PrasadG193 commented Oct 18, 2019

@daegeun-ha By design ping and kubectl commands are expected to run anywhere. To execute kubectl commands outside of configured channel, you have to pass --cluster-name flag. ping command can run without --cluster-name flag. Please execute /botkubehelp if you have configured Slash command in Mattermost
https://www.botkube.io/installation/mattermost/#h-install-BotKube-slashcommand
Please see: https://www.botkube.io/usage/#h-specify-cluster-name

@daegeun-ha

This comment has been minimized.

Copy link
Author

@daegeun-ha daegeun-ha commented Oct 23, 2019

I checked it. Thanks :)

@daegeun-ha daegeun-ha closed this Oct 23, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.